[JBoss JIRA] Created: (JBRULES-2504) Maven: clean up the maven build and prepare for maven 3 (multi-issue)
1:19 p.m.
Maven: clean up the maven build and prepare for maven 3 (multi-issue)
---------------------------------------------------------------------
Key: JBRULES-2504
URL: https://jira.jboss.org/jira/browse/JBRULES-2504
Project: Drools
Issue Type: Task
Security Level: Public (Everyone can see)
Components: All
Affects Versions: 5.1.0.M1
Reporter: Geoffrey De Smet
Assignee: Geoffrey De Smet
Priority: Minor
Fix For: FUTURE
This is a list of the smaller issues:
* Don't use compile dependencies for dependencies that should be purely transitive
dependencies
* Don't use <optional> in <dependencyManagement>
** might not already be the case
* All of the generated files should be in the target directory
** guvnor: version file etc
** several modules (osgi based?): MANIFEST.MF
Bigger issues are linked.
--
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
1:55 p.m.
New subject: [JBoss JIRA] Updated: (JBRULES-2504) Maven: clean up the maven build and prepare for maven 3 (multi-issue)
[
https://jira.jboss.org/jira/browse/JBRULES-2504?page=com.atlassian.jira.p...
]
Geoffrey De Smet updated JBRULES-2504:
--------------------------------------
Description:
This is a list of the smaller issues:
* Don't use compile dependencies for dependencies that should be purely transitive
dependencies
* Don't use <optional> in <dependencyManagement>
* Don't set <version> of dependencies in child pom's, only in
<dependencyManagement> of the drools parent pom
** might not already be the case
* All of the generated files should be in the target directory
** guvnor: version file etc
** several modules (osgi based?): MANIFEST.MF
Bigger issues are linked.
was:
This is a list of the smaller issues:
* Don't use compile dependencies for dependencies that should be purely transitive
dependencies
* Don't use <optional> in <dependencyManagement>
** might not already be the case
* All of the generated files should be in the target directory
** guvnor: version file etc
** several modules (osgi based?): MANIFEST.MF
Bigger issues are linked.
Maven: clean up the maven build and prepare for maven 3
(multi-issue)
---------------------------------------------------------------------
Key: JBRULES-2504
URL: https://jira.jboss.org/jira/browse/JBRULES-2504
Project: Drools
Issue Type: Task
Security Level: Public(Everyone can see)
Components: All
Affects Versions: 5.1.0.M1
Reporter: Geoffrey De Smet
Assignee: Geoffrey De Smet
Priority: Minor
Fix For: FUTURE
This is a list of the smaller issues:
* Don't use compile dependencies for dependencies that should be purely transitive
dependencies
* Don't use <optional> in <dependencyManagement>
* Don't set <version> of dependencies in child pom's, only in
<dependencyManagement> of the drools parent pom
** might not already be the case
* All of the generated files should be in the target directory
** guvnor: version file etc
** several modules (osgi based?): MANIFEST.MF
Bigger issues are linked.
--
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
11:29 a.m.
New subject: [JBoss JIRA] Commented: (JBRULES-2504) Maven: clean up the maven build and prepare for maven 3 (multi-issue)
[
https://jira.jboss.org/browse/JBRULES-2504?page=com.atlassian.jira.plugin...
]
Geoffrey De Smet commented on JBRULES-2504:
-------------------------------------------
From mailing list:
The tests can't run because the
drools-camel module has a dependency on spring 2.5.5.
This version is then mixed with version 2.5.6 from other dependencies. Simple fix is to
change drools-camel to use spring 2.5.6.
But we should really be using Maven dependency management at the root level to avoid this
problem.
In general there should not be any version numbers in any of the sub-modules.
Maven: clean up the maven build and prepare for maven 3
(multi-issue)
---------------------------------------------------------------------
Key: JBRULES-2504
URL: https://jira.jboss.org/browse/JBRULES-2504
Project: Drools
Issue Type: Task
Security Level: Public(Everyone can see)
Components: All
Affects Versions: 5.1.0.M1
Reporter: Geoffrey De Smet
Assignee: Geoffrey De Smet
Priority: Minor
Fix For: FUTURE
This is a list of the smaller issues:
* Don't use compile dependencies for dependencies that should be purely transitive
dependencies
* Don't use <optional> in <dependencyManagement>
* Don't set <version> of dependencies in child pom's, only in
<dependencyManagement> of the drools parent pom
** might not already be the case
* All of the generated files should be in the target directory
** guvnor: version file etc
** several modules (osgi based?): MANIFEST.MF
Bigger issues are linked.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
6:18 p.m.
New subject: [JBoss JIRA] Updated: (JBRULES-2504) Maven: clean up the maven build and prepare for maven 3 (multi-issue)
[
https://jira.jboss.org/browse/JBRULES-2504?page=com.atlassian.jira.plugin...
]
Mark Proctor updated JBRULES-2504:
----------------------------------
Fix Version/s: 5.2.0.M1
(was: FUTURE)
Maven: clean up the maven build and prepare for maven 3
(multi-issue)
---------------------------------------------------------------------
Key: JBRULES-2504
URL: https://jira.jboss.org/browse/JBRULES-2504
Project: Drools
Issue Type: Task
Security Level: Public(Everyone can see)
Components: All
Affects Versions: 5.1.0.M1
Reporter: Geoffrey De Smet
Assignee: Geoffrey De Smet
Priority: Minor
Fix For: 5.2.0.M1
This is a list of the smaller issues:
* Don't use compile dependencies for dependencies that should be purely transitive
dependencies
* Don't use <optional> in <dependencyManagement>
* Don't set <version> of dependencies in child pom's, only in
<dependencyManagement> of the drools parent pom
** might not already be the case
* All of the generated files should be in the target directory
** guvnor: version file etc
** several modules (osgi based?): MANIFEST.MF
Bigger issues are linked.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
3:45 a.m.
New subject: [JBoss JIRA] Commented: (JBRULES-2504) Maven: clean up the maven build and prepare for maven 3 (multi-issue)
[
https://jira.jboss.org/browse/JBRULES-2504?page=com.atlassian.jira.plugin...
]
Geoffrey De Smet commented on JBRULES-2504:
-------------------------------------------
The build is now on maven 3, but there's still a bunch of stuff to clean up
Maven: clean up the maven build and prepare for maven 3
(multi-issue)
---------------------------------------------------------------------
Key: JBRULES-2504
URL: https://jira.jboss.org/browse/JBRULES-2504
Project: Drools
Issue Type: Task
Security Level: Public(Everyone can see)
Components: All
Affects Versions: 5.1.0.M1
Reporter: Geoffrey De Smet
Assignee: Geoffrey De Smet
Priority: Minor
Fix For: 5.2.0.M1
This is a list of the smaller issues:
* Don't use compile dependencies for dependencies that should be purely transitive
dependencies
* Don't use <optional> in <dependencyManagement>
* Don't set <version> of dependencies in child pom's, only in
<dependencyManagement> of the drools parent pom
** might not already be the case
* All of the generated files should be in the target directory
** guvnor: version file etc
** several modules (osgi based?): MANIFEST.MF
Bigger issues are linked.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
10:46 a.m.
New subject: [JBoss JIRA] Resolved: (JBRULES-2504) Maven: clean up the maven build and prepare for maven 3 (multi-issue)
[
https://issues.jboss.org/browse/JBRULES-2504?page=com.atlassian.jira.plug...
]
Geoffrey De Smet resolved JBRULES-2504.
---------------------------------------
Fix Version/s: 5.2.0.M2
(was: 5.2.0.M1)
Resolution: Done
We're on maven 3 a while now.
Maven: clean up the maven build and prepare for maven 3
(multi-issue)
---------------------------------------------------------------------
Key: JBRULES-2504
URL: https://issues.jboss.org/browse/JBRULES-2504
Project: Drools
Issue Type: Task
Security Level: Public(Everyone can see)
Components: All
Affects Versions: 5.1.0.M1
Reporter: Geoffrey De Smet
Assignee: Geoffrey De Smet
Priority: Minor
Fix For: 5.2.0.M2
This is a list of the smaller issues:
* Don't use compile dependencies for dependencies that should be purely transitive
dependencies
* Don't use <optional> in <dependencyManagement>
* Don't set <version> of dependencies in child pom's, only in
<dependencyManagement> of the drools parent pom
** might not already be the case
* All of the generated files should be in the target directory
** guvnor: version file etc
** several modules (osgi based?): MANIFEST.MF
Bigger issues are linked.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
4996
days inactive
5357
days old
5 comments
2 participants
participants (2)
-
Geoffrey De Smet (JIRA) -
Mark Proctor (JIRA)