You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@felix.apache.org by "Carlos Sanchez (JIRA)" <ji...@apache.org> on 2007/05/15 00:49:16 UTC
[jira] Created: (FELIX-282) Use remote resources plugin to avoid
having many copies of licenses and notices
Use remote resources plugin to avoid having many copies of licenses and notices
-------------------------------------------------------------------------------
Key: FELIX-282
URL: https://issues.apache.org/jira/browse/FELIX-282
Project: Felix
Issue Type: Improvement
Reporter: Carlos Sanchez
Adding the remote resources plugin to the parent pom the license file is added automatically and the notice files are generated
I tried it with the bundle plugin, deleting the notice and license from src/main/resources. The notice is a bit different so just take a look to see if it's ok.
I also added the relativePath to <parent> in the plugin so it builds from svn without installing the parent pom
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (FELIX-282) Use remote resources plugin to avoid
having many copies of licenses and notices
Posted by "Richard S. Hall (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/FELIX-282?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12515771 ]
Richard S. Hall commented on FELIX-282:
---------------------------------------
Isn't this complete now?
> Use remote resources plugin to avoid having many copies of licenses and notices
> -------------------------------------------------------------------------------
>
> Key: FELIX-282
> URL: https://issues.apache.org/jira/browse/FELIX-282
> Project: Felix
> Issue Type: Improvement
> Reporter: Carlos Sanchez
> Attachments: NOTICE, remote-resources.patch
>
>
> Adding the remote resources plugin to the parent pom the license file is added automatically and the notice files are generated
> I tried it with the bundle plugin, deleting the notice and license from src/main/resources. The notice is a bit different so just take a look to see if it's ok.
> I also added the relativePath to <parent> in the plugin so it builds from svn without installing the parent pom
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (FELIX-282) Use remote resources plugin to avoid
having many copies of licenses and notices
Posted by "Karl Pauls (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/FELIX-282?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12511790 ]
Karl Pauls commented on FELIX-282:
----------------------------------
I tried to apply this patch but I get the following error in all subprojects that use our bundleplugin,
[WARNING] Attempting to build MavenProject instance for Artifact of type: jar; constructing POM artifact instead.
[INFO] ------------------------------------------------------------------------
[ERROR] FATAL ERROR
[INFO] ------------------------------------------------------------------------
[INFO] org.apache.maven.model.Repository
[INFO] ------------------------------------------------------------------------
[INFO] Trace
java.lang.ClassCastException: org.apache.maven.model.Repository
at org.apache.maven.artifact.repository.metadata.DefaultRepositoryMetadataManager.mergeMetadata(DefaultRepositoryMetadataManager.java:161)
at org.apache.maven.artifact.repository.metadata.DefaultRepositoryMetadataManager.resolve(DefaultRepositoryMetadataManager.java:134)
at org.apache.maven.artifact.transform.AbstractVersionTransformation.resolveVersion(AbstractVersionTransformation.java:65)
at org.apache.maven.artifact.transform.SnapshotTransformation.transformForResolve(SnapshotTransformation.java:63)
at org.apache.maven.artifact.transform.DefaultArtifactTransformationManager.transformForResolve(DefaultArtifactTransformationManager.java:57)
at org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolve(DefaultArtifactResolver.java:114)
at org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolve(DefaultArtifactResolver.java:73)
at org.apache.maven.project.DefaultMavenProjectBuilder.findModelFromRepository(DefaultMavenProjectBuilder.java:526)
at org.apache.maven.project.DefaultMavenProjectBuilder.buildFromRepository(DefaultMavenProjectBuilder.java:234)
at org.apache.maven.plugin.resources.remote.ProcessRemoteResourcesMojo.getProjects(ProcessRemoteResourcesMojo.java:362)
at org.apache.maven.plugin.resources.remote.ProcessRemoteResourcesMojo.configureVelocityContext(ProcessRemoteResourcesMojo.java:489)
at org.apache.maven.plugin.resources.remote.ProcessRemoteResourcesMojo.execute(ProcessRemoteResourcesMojo.java:293)
at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:443)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:539)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:480)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:459)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:311)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:278)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:143)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:334)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:125)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:272)
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:585)
at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
> Use remote resources plugin to avoid having many copies of licenses and notices
> -------------------------------------------------------------------------------
>
> Key: FELIX-282
> URL: https://issues.apache.org/jira/browse/FELIX-282
> Project: Felix
> Issue Type: Improvement
> Reporter: Carlos Sanchez
> Attachments: NOTICE, remote-resources.patch
>
>
> Adding the remote resources plugin to the parent pom the license file is added automatically and the notice files are generated
> I tried it with the bundle plugin, deleting the notice and license from src/main/resources. The notice is a bit different so just take a look to see if it's ok.
> I also added the relativePath to <parent> in the plugin so it builds from svn without installing the parent pom
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (FELIX-282) Use remote resources plugin to avoid
having many copies of licenses and notices
Posted by "Carlos Sanchez (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/FELIX-282?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12495829 ]
Carlos Sanchez commented on FELIX-282:
--------------------------------------
> I am somewhat confused about this. Does this mean if we apply this patch we should remove the LICENSE and NOTICE files from the various subprojects now?
you are right
> Doesn't the NOTICE file include stuff about licenses/copyrights of third-party dependencies?
yes
> So, it seems like NOTICE files cannot be generated, can it?
they can, kind of, as long as they are not very complex
it uses a template that it's defined in http://repo1.maven.org/maven2/org/apache/apache-jar-resource-bundle/1.2/apache-jar-resource-bundle-1.2.jar
> Use remote resources plugin to avoid having many copies of licenses and notices
> -------------------------------------------------------------------------------
>
> Key: FELIX-282
> URL: https://issues.apache.org/jira/browse/FELIX-282
> Project: Felix
> Issue Type: Improvement
> Reporter: Carlos Sanchez
> Attachments: NOTICE, remote-resources.patch
>
>
> Adding the remote resources plugin to the parent pom the license file is added automatically and the notice files are generated
> I tried it with the bundle plugin, deleting the notice and license from src/main/resources. The notice is a bit different so just take a look to see if it's ok.
> I also added the relativePath to <parent> in the plugin so it builds from svn without installing the parent pom
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (FELIX-282) Use remote resources plugin to avoid
having many copies of licenses and notices
Posted by "Carlos Sanchez (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/FELIX-282?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Carlos Sanchez updated FELIX-282:
---------------------------------
Attachment: NOTICE
sample notice
> Use remote resources plugin to avoid having many copies of licenses and notices
> -------------------------------------------------------------------------------
>
> Key: FELIX-282
> URL: https://issues.apache.org/jira/browse/FELIX-282
> Project: Felix
> Issue Type: Improvement
> Reporter: Carlos Sanchez
> Attachments: NOTICE, remote-resources.patch
>
>
> Adding the remote resources plugin to the parent pom the license file is added automatically and the notice files are generated
> I tried it with the bundle plugin, deleting the notice and license from src/main/resources. The notice is a bit different so just take a look to see if it's ok.
> I also added the relativePath to <parent> in the plugin so it builds from svn without installing the parent pom
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (FELIX-282) Use remote resources plugin to avoid
having many copies of licenses and notices
Posted by "Carlos Sanchez (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/FELIX-282?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12495806 ]
Carlos Sanchez commented on FELIX-282:
--------------------------------------
btw, i updated license, names and other info in some poms in the repo so the notice is correctly generated. To get the fixed ones you have to delete junit and bnd poms in the local repo.
> Use remote resources plugin to avoid having many copies of licenses and notices
> -------------------------------------------------------------------------------
>
> Key: FELIX-282
> URL: https://issues.apache.org/jira/browse/FELIX-282
> Project: Felix
> Issue Type: Improvement
> Reporter: Carlos Sanchez
> Attachments: remote-resources.patch
>
>
> Adding the remote resources plugin to the parent pom the license file is added automatically and the notice files are generated
> I tried it with the bundle plugin, deleting the notice and license from src/main/resources. The notice is a bit different so just take a look to see if it's ok.
> I also added the relativePath to <parent> in the plugin so it builds from svn without installing the parent pom
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (FELIX-282) Use remote resources plugin to avoid
having many copies of licenses and notices
Posted by "Richard S. Hall (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/FELIX-282?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12495820 ]
Richard S. Hall commented on FELIX-282:
---------------------------------------
I am somewhat confused about this. Does this mean if we apply this patch we should remove the LICENSE and NOTICE files from the various subprojects now?
Doesn't the NOTICE file include stuff about licenses/copyrights of third-party dependencies? So, it seems like NOTICE files cannot be generated, can it?
> Use remote resources plugin to avoid having many copies of licenses and notices
> -------------------------------------------------------------------------------
>
> Key: FELIX-282
> URL: https://issues.apache.org/jira/browse/FELIX-282
> Project: Felix
> Issue Type: Improvement
> Reporter: Carlos Sanchez
> Attachments: remote-resources.patch
>
>
> Adding the remote resources plugin to the parent pom the license file is added automatically and the notice files are generated
> I tried it with the bundle plugin, deleting the notice and license from src/main/resources. The notice is a bit different so just take a look to see if it's ok.
> I also added the relativePath to <parent> in the plugin so it builds from svn without installing the parent pom
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (FELIX-282) Use remote resources plugin to avoid
having many copies of licenses and notices
Posted by "Carlos Sanchez (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/FELIX-282?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Carlos Sanchez updated FELIX-282:
---------------------------------
Attachment: remote-resources.patch
> Use remote resources plugin to avoid having many copies of licenses and notices
> -------------------------------------------------------------------------------
>
> Key: FELIX-282
> URL: https://issues.apache.org/jira/browse/FELIX-282
> Project: Felix
> Issue Type: Improvement
> Reporter: Carlos Sanchez
> Attachments: remote-resources.patch
>
>
> Adding the remote resources plugin to the parent pom the license file is added automatically and the notice files are generated
> I tried it with the bundle plugin, deleting the notice and license from src/main/resources. The notice is a bit different so just take a look to see if it's ok.
> I also added the relativePath to <parent> in the plugin so it builds from svn without installing the parent pom
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.