Commits

Show all
Author Commit Message Labels Comments Date
Dylan Etkin
[maven-release-plugin] prepare release atlassian-plugins-parent-2.6.0-alpha5
Tags
atlassian-plugins-parent-2.6.0-alpha5
Dylan Etkin
PLUG-599 - the implementation of looking up the file names with a wildcard was broken. When the class was in a jar we were getting a file reference from within the jar and were not able to read from that directory. Even if we could read it it would not have given us files in other locations that might contain that package. I have changed the implementation to look for all files with the single filename that are on the classpath. Not quite as nice but it does work.
pi songsiritat
[maven-release-plugin] prepare for next development iteration
pi songsiritat
[maven-release-plugin] prepare release atlassian-plugins-parent-2.6.0-alpha4
Tags
atlassian-plugins-parent-2.6.0-alpha4
Don Brown
PLUG-616: Add jcl-over-slf4j as a framework bundle to fix logging problems
Jed Wesley-Smith
PLUG-599 extracted loading of metadata from the classpath from the DefaultPluginMetadataManager into the PluginMetadata interface and ClasspathPluginMetadata implementation
Don Brown
Removing empty directories
Don Brown
PLUG-625: Moving refimpl over to refapp
Jed Wesley-Smith
generics: added ModuleDescriptor generic type parameter <?>
Jed Wesley-Smith
minor source cleanup, enhanced for use, final everything, no tabs
Jed Wesley-Smith
added *.iml files to svn:ignore
Dylan Etkin
[maven-release-plugin] prepare for next development iteration
Dylan Etkin
[maven-release-plugin] prepare release atlassian-plugins-parent-2.6.0-alpha3
Tags
atlassian-plugins-parent-2.6.0-alpha3
Dylan Etkin
PLUG-599 - crap. I figured that the refapp would manage its own plugin container. I was wrong. Now exposing the PluginMetadataManager to the refimpl.
Dylan Etkin
[maven-release-plugin] prepare for next development iteration
Dylan Etkin
[maven-release-plugin] prepare release atlassian-plugins-parent-2.6.0-alpha2
Tags
atlassian-plugins-parent-2.6.0-alpha2
Dylan Etkin
PLUG-599 - added a mechanism for host applications to specify required plugins and modules and to tell the plugins system which plugins have come from the host application. See https://studio.atlassian.com/source/cru/CR-PLUG-202 and https://studio.atlassian.com/source/cru/CR-PLUG-200 for more details.
Don Brown
PLUG-620: Fix event publisher to use actual impl
Don Brown
PLUG-620: Exposing the EventPublisher as a host component for the refimpl
Richard Wallace
PLUG-622 make sure the unloadable plugin is faithful to the original plugins dynamically loaded property
Don Brown
[maven-release-plugin] prepare for next development iteration
Don Brown
[maven-release-plugin] prepare release atlassian-plugins-parent-2.6.0-alpha1
Tags
atlassian-plugins-parent-2.6.0-alpha1
Andreas Knecht
PLUG-619: Expiry headers should be in seconds and the HTTP spec notes that they should not exceed 1 year.
George Barnett
Don says atlassian.org.osgi.framework.bootdelegation should be default. Lets try
George Barnett
Change Jprofiler to use Dynamic Sampling
George Barnett
Removed the setup/fixedload config. No setup test in P2
George Barnett
Updated JProfiler config
George Barnett
Bump plugins 2.0 to Jprofiler 6. Add more classes to boot delegation
Brenden Bain
Removing some warnings from the code by adding some generics. There is no functional difference.
Brenden Bain
PLUG-617: Warn people when it takes a long time to enable a plugin when in dev mode. We bumped this timeout from 5 to 30 seconds because the gadget publisher in JIRA can take this long to load when running java in DEBUG mode. We are also now going to log a message about slow startup since 30 seconds is a long time to wait for your plugin to fail.
  1. Prev
  2. Next