Re: upgrading to Jackrabbit 2.2.5

Craig Ganoe Tue, 12 Apr 2011 08:28:54 -0700

I have not been able to build Sling for the past couple of weeks. I grabbed everything fresh on Friday, and am still getting these errors:


[INFO] Scanning for projects...
[WARNING]

[WARNING] Some problems were encountered while building the effective model for org.apache.sling:org.apache.sling.testing.samples.integrationtests:jar: 0.1.1-SNAPSHOT [WARNING] 'dependencies.dependency. (groupId:artifactId:type:classifier)' must be unique: org.apache.sling:org.apache.sling.junit.remote:jar -> duplicate declaration of version 0.1.1-SNAPSHOT @ line 272, column 21

[WARNING]

[WARNING] It is highly recommended to fix these problems because they threaten the stability of your build.

[WARNING]

[WARNING] For this reason, future Maven versions might no longer support building such malformed projects.

[WARNING]
[INFO]


===================================
Then further on in the build I get:

-------------------------------------------------------
 T E S T S
-------------------------------------------------------
Running org.apache.sling.commons.log.internal.slf4j.SlingLoggerTest

Tests run: 6, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.028 sec Running org.apache.sling.commons.log.internal.slf4j.SizeLimitedFileRotatorTest Tests run: 5, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.015 sec

Running org.apache.sling.commons.log.internal.slf4j.SlingLogWriterTest

Tests run: 6, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.026 sec


Results :

Tests run: 17, Failures: 0, Errors: 0, Skipped: 0

[INFO]

[INFO] --- maven-bundle-plugin:2.0.1:bundle (default-bundle) @ org.apache.sling.commons.log ---

java.lang.reflect.InvocationTargetException
        at sun.reflect.GeneratedMethodAccessor56.invoke(Unknown Source)

at sun .reflect .DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java: 25)

        at java.lang.reflect.Method.invoke(Method.java:597)
        at aQute.lib.osgi.Macro.doCommand(Macro.java:183)
        at aQute.lib.osgi.Macro.doCommands(Macro.java:171)
        at aQute.lib.osgi.Macro.replace(Macro.java:118)
        at aQute.lib.osgi.Macro.process(Macro.java:62)
        at aQute.lib.osgi.Macro.process(Macro.java:78)
        at aQute.lib.osgi.Macro.process(Macro.java:48)
        at aQute.lib.osgi.Macro.process(Macro.java:43)
        at aQute.lib.osgi.Processor.getProperty(Processor.java:609)
        at aQute.lib.osgi.Processor.getProperty(Processor.java:387)
        at aQute.lib.osgi.Analyzer.getImportPackages(Analyzer.java:248)
        at aQute.lib.osgi.Builder.getImportPackages(Builder.java:149)
        at aQute.lib.osgi.Analyzer.analyze(Analyzer.java:146)
        at aQute.lib.osgi.Builder.analyze(Builder.java:198)
        at aQute.lib.osgi.Analyzer.calcManifest(Analyzer.java:283)
        at aQute.lib.osgi.Builder.build(Builder.java:78)

at org .apache .felix.bundleplugin.BundlePlugin.buildOSGiBundle(BundlePlugin.java:395) at org.apache.felix.bundleplugin.BundlePlugin.execute(BundlePlugin.java: 286) at org.apache.felix.bundleplugin.BundlePlugin.execute(BundlePlugin.java: 240) at org.apache.felix.bundleplugin.BundlePlugin.execute(BundlePlugin.java: 231) at org .apache .maven .plugin .DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java: 107) 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:534)
        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) Caused by: java.lang.IllegalArgumentException: Invalid syntax for version: ${@}

        at aQute.libg.version.Version.<init>(Version.java:45)
        at aQute.lib.osgi.Macro._version(Macro.java:627)
        ... 43 more
java.lang.reflect.InvocationTargetException
        at sun.reflect.GeneratedMethodAccessor56.invoke(Unknown Source)

at sun .reflect .DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java: 25)

        at java.lang.reflect.Method.invoke(Method.java:597)
        at aQute.lib.osgi.Macro.doCommand(Macro.java:183)
        at aQute.lib.osgi.Macro.doCommands(Macro.java:171)
        at aQute.lib.osgi.Macro.replace(Macro.java:118)
        at aQute.lib.osgi.Macro.process(Macro.java:62)
        at aQute.lib.osgi.Macro.process(Macro.java:78)
        at aQute.lib.osgi.Macro.process(Macro.java:48)
        at aQute.lib.osgi.Macro.process(Macro.java:43)
        at aQute.lib.osgi.Processor.getProperty(Processor.java:609)
        at aQute.lib.osgi.Processor.getProperty(Processor.java:387)
        at aQute.lib.osgi.Analyzer.getImportPackages(Analyzer.java:248)
        at aQute.lib.osgi.Builder.getImportPackages(Builder.java:149)
        at aQute.lib.osgi.Analyzer.analyze(Analyzer.java:146)
        at aQute.lib.osgi.Builder.analyze(Builder.java:198)
        at aQute.lib.osgi.Analyzer.calcManifest(Analyzer.java:283)
        at aQute.lib.osgi.Builder.build(Builder.java:78)

        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:534)
        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 aQute.libg.version.Version.<init>(Version.java:45)
        at aQute.lib.osgi.Macro._version(Macro.java:627)
        ... 43 more

[WARNING] Warning building bundle org.apache.sling:org.apache.sling.commons.log:bundle:2.1.3-SNAPSHOT : No translation found for macro: @ [WARNING] Warning building bundle org.apache.sling:org.apache.sling.commons.log:bundle:2.1.3-SNAPSHOT : Exception in replace: java.lang.IllegalArgumentException: Invalid syntax for version: ${@} [WARNING] Warning building bundle org.apache.sling:org.apache.sling.commons.log:bundle:2.1.3-SNAPSHOT : No translation found for macro: version;==;${@} [WARNING] Warning building bundle org.apache.sling:org.apache.sling.commons.log:bundle:2.1.3-SNAPSHOT : No translation found for macro: version;=+;${@}

[INFO]

[INFO] >>> maven-source-plugin:2.1.1:jar (attach-sources) @ org.apache.sling.commons.log >>>

[INFO]

I'm kind of at a loss as to what to do next. I used to be able to build Sling without these issues.



On Apr 2, 2011, at 2:18 PM, Eric Norman wrote:

Hi Craig,
I think we worked through all the issues for (SLING-2044) and upgraded to
jackrabbit 2.2.5 in revision 1088070.  Please let us know if you find
anything that is broken.

Regards,
Eric

On Thu, Mar 31, 2011 at 2:43 PM, Craig Ganoe <[email protected]> wrote:
As I said in one of my longer emails, the only Sling code change I noticed
is that Sling's PluggableDefaultAccessManager makes a call to
canRead(itemPath) on its superclass in Jackrabbit - DefaultAccessManager. For some reason unclear to me they changed it in from just taking a path as a parameter in 2.1 to taking both a path and an item ID in 2.2, but then the
JavaDocs say either one of the parameters can be null.
I made a little progress today, but unfortunately, due to the absurdities of today's build tools, I'm stuck with a bunch of vague messages that have nothing to do with actually building the software. That today you can't replace a few libraries and a few lines of code and still build software without causing miles of vague errors that have nothing to do with the
compilability of the actual code is ridiculous.

[INFO] Scanning for projects...
[WARNING]
[WARNING] Some problems were encountered while building the effective model
for
org .apache.sling:org.apache.sling.testing.samples.integrationtests:jar: 0.1.1-SNAPSHOT [WARNING] 'dependencies.dependency. (groupId:artifactId:type:classifier)'
must be unique: org.apache.sling:org.apache.sling.junit.remote:jar ->
duplicate declaration of version 0.1.1-SNAPSHOT @ line 272, column 21
[WARNING] 'dependencies.dependency. (groupId:artifactId:type:classifier)' must be unique: org.apache.sling:org.apache.sling.testing.tools:jar ->
duplicate declaration of version 0.1.1-SNAPSHOT @ line 277, column 21
[WARNING]
[WARNING] It is highly recommended to fix these problems because they
threaten the stability of your build.
[WARNING]
[WARNING] For this reason, future Maven versions might no longer support
building such malformed projects.
[WARNING]


On Mar 31, 2011, at 2:24 PM, Eric Norman wrote:
Hi All,
I found a use case where I could also use an upgrade to jackrabbit 2.2.5
to
utilize some changes in user/group management.  I filed JIRA
issue SLING-2044 for tracking and will attempt the upgrade today.

Regards,
Eric

On Fri, Mar 25, 2011 at 8:23 AM, Justin Edelson <[email protected]
wrote:
On Fri, Mar 25, 2011 at 9:03 AM, Ian Boston <[email protected]> wrote:
On 25 Mar 2011, at 12:54, Justin Edelson wrote:
On Mar 24, 2011, at 5:06 PM, Ian Boston <[email protected]> wrote:
On 24 Mar 2011, at 20:44, Craig Ganoe wrote:
Is there any documentation for upgrading the jackrabbit version in
the
Sling build?
AFAIK, there is not.
Ian
There is, in a sense. Look at JIRA and Subversion and you'll see the
exact set of changes made for prior upgrades.
good point,
https://issues.apache.org/jira/browse/SLING-1660?page=com.atlassian.jira.plugin.ext.subversion%3Asubversion-commits-tabpanel #issue-tabs
http://svn.apache.org/viewvc?view=revision&revision=987559

was that the right issue ?
SLING-1531 too...
Ian
Justin
Thanks.

Craig

smime.p7s
Description: S/MIME cryptographic signature

Re: upgrading to Jackrabbit 2.2.5

Reply via email to