Thanks for looking into this Stuart.
Indeed the release.xml is now updated.
My local maven repository contains quite a few versions of the
maven-bundle-plugin (from 1.4.0 to 2.3.6) and of bundlerepository (from
1.0.3 to 1.6.6) including some snapshots for each..
My parent pom points to maven-bundle-plugin version 2.3.5 which in turn
points to bundlerepository version 1.6.6.. but you're right, it doesn't
match the code so I'm not sure what version is used.
So now I just need the write permissions for confluence and I think I'll
be through with my first release :)
thanks,
arjun
On 02/03/2012 03:06 PM, Stuart McCulloch wrote:
On 3 Feb 2012, at 09:44, Arjun Panday wrote:
Two more things:
I didn't have account on confluence so I simply signed up, but that doesn't
give write permissions to update the news and download sections. Can someone
please unlock this for me? (Marcel?)
Also there seem to be an issue with the OBR update. The maven command exited with
"Build success" just after dumping a NullPointerException, so I checked the
file people.apache.org:/www/felix.apache.org/obr/releases.xml and it doesn't seem to
contain any reference to my plugin and it is still dated Jul 10 2011.
I tried the same command locally after checking out the
https://svn.apache.org/repos/asf/felix/releases/org.apache.felix.servicediagnostics.plugin-0.1.1
tag and didn't see the NPE
The other odd thing is that the line DataModelHelperImpl.java:875 doesn't
appear to match any public release of the bundlerepository
For info:
[WARNING] Exception while updating remote OBR: null
java.lang.NullPointerException
at
org.apache.felix.bundlerepository.impl.DataModelHelperImpl.getSymbolicName(DataModelHelperImpl.java:875)
at
org.apache.felix.bundlerepository.impl.DataModelHelperImpl.populate(DataModelHelperImpl.java:521)
at
org.apache.felix.bundlerepository.impl.DataModelHelperImpl.createResource(DataModelHelperImpl.java:515)
at
org.apache.felix.bundlerepository.impl.DataModelHelperImpl.createResource(DataModelHelperImpl.java:406)
at org.apache.felix.obrplugin.ObrUpdate.updateRepository(ObrUpdate.java:170)
at
org.apache.felix.obrplugin.ObrDeploy.updateRemoteBundleMetadata(ObrDeploy.java:352)
at org.apache.felix.obrplugin.ObrDeploy.execute(ObrDeploy.java:254)
at
org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:101)
at
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:209)
at
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
at
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
at
org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:84)
at
org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:59)
at
org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBuild(LifecycleStarter.java:183)
at
org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:161)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:319)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:156)
at org.apache.maven.cli.MavenCli.execute(MavenCli.java:537)
at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:196)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:141)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at
org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:290)
at
org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:230)
at
org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:409)
at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:352)
[INFO] UNLOCK scp://people.apache.org/www/felix.apache.org/obr/releases.xml
[INFO] ------------------------------------------------------------------------
[INFO] BUILD SUCCESS
[INFO] ------------------------------------------------------------------------
thanks,
Arjun
On 02/03/2012 09:48 AM, Arjun Panday wrote:
Hi,
I'm not sure if I've done something stupid now!
The doc reads:
"login to https://repository.apache.org with your Apache SVN
credentials. Click on Staging. Find your closed staging repository,
right click on it and choose Promote. Select the Releases repository
from the drop-down list and click Promote."
But the Promote button was not available on my closed staging repo; only
the release button was... so I tried that one :)
"next click on Repositories, select the Releases repository and validate
that your artifacts are all there"
Yes, they are..
What about the promote button?
Did I miss something here?
thanks,
Arjun
On 02/01/2012 02:17 PM, Arjun Panday wrote:
Hi,
I'm closing the vote.
The vote has passed with:
+1 (binding) from Carsten Ziegeler, Stuart McCulloch and Richard Hall
+1 (non binding) from Pierre De Rop and Ken Gilmer
I'll proceed to promote the release.
Thanks a lot everyone.
Arjun
On 02/01/2012 11:42 AM, Stuart McCulloch wrote:
On 1 Feb 2012, at 10:24, Arjun Panday<[email protected]>
wrote:
On 01/31/2012 11:26 PM, Stuart McCulloch wrote:
On 31 Jan 2012, at 22:06, Richard S. Hall wrote:
+1
The NOTICE file is a little messed up in the plugin, it seems to repeat itself.
The copyright year should be updated to 2012 in both NOTICE and DEPENDENCIES.
-> richard
p.s. That's a really big bundle...8.5MB... :-)
To be fair ~8mb of that is the Scala runtime... maybe that should be separated
into its own bundle in case others want to re-use it?
Exactly, plus a bit of javascript libraries.. the plugin itself is quite small.
Unfortunately the scala runtime doesn't come readily packaged as an OSGi bundle.
The original project didn't embed the scala runtime; it came with a readme file
to explain how to wrap the scala library using bnd. But for the release, in
order to have something readily useable, I decided to embed the scala library.
It's a packaging issue.
I wouldn't mind creating a new module just for the scala library, outside the
service diagnostics sub-project, so that other sub-projects can use scala.
I think I'll go ahead with this release for now and maybe I can issue a new
JIRA for the scala library packaging?
Sounds good to me, definitely go ahead with this release - it was just a
thought for future development.
thanks,
-arjun
On 1/20/12 03:59 , Arjun Panday wrote:
Hi everyone,
Second attempt at releasing the Service Diagnostics WebConsole Plugin.
I've simply refactored the POMs by moving the parent role out of the reactor
POM. The directory structure seems cleaner. Let me know.
Here's the staging repository:
https://repository.apache.org/content/repositories/orgapachefelix-110/
You can use this UNIX script to download the release and verify the signatures:
http://svn.apache.org/repos/asf/felix/trunk/check_staged_release.sh
Usage:
sh check_staged_release.sh 010 /tmp/felix-staging
Please vote to approve this release:
[ ] +1 Approve the release
[ ] -1 Veto the release (please provide specific comments)
This vote will be open for 72 hours.
Thanks,
-arjun
