[
https://jira.jboss.org/jira/browse/JBAS-5695?page=com.atlassian.jira.plug...
]
Paul Gier commented on JBAS-5695:
---------------------------------
I probably won't be able to fix all the poms but a lot of them are duplicates using
the same license (apache, gpl, etc), so I can put in the repository at least one pom for
each of the licenses that we downloaded in the old build. I got most of them Friday, but
I can find the last ones Monday, and if there are any problems, then I we can just
manually copy the licenses that we need into the build.
Licenses not available for release packaging
--------------------------------------------
Key: JBAS-5695
URL:
https://jira.jboss.org/jira/browse/JBAS-5695
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Build System
Affects Versions: JBossAS-5.0.0.CR1
Reporter: Rajesh Rajasekaran
Assignee: Paul Gier
Priority: Blocker
Fix For: JBossAS-5.0.0.CR2
Building the release bundle
build> ant -f build-release.xml release expects all the licenses to be present under
thirdparty/licences folder.
I think this was handled by the buildmagic thirdparty download mechanism earlier of
downloading the licenses.
How do we want to handle this with maven2?
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira