Hi guys, We have a maven project in Qpid svn root [1]. At the moment it does not have much attention and care. Thus, it contains outdated information. Only Qpid java components depend on it at the moment.
I am going to remove that dependency in qpid-java-6 and move some of useful parent pom functionality into qpid-java pom.xml in order to implement some urgent changes to license generation and checks reported as blocker [2]. Otherwise, we need to release a new parent pom version with the changes. That requires separate release process, including voting, which is unnecessary overhead to our release process. When I remove the dependency to Qpid parent pom from qpid-java, it will became unused and potentially could be deleted. Shall we delete it? Any thoughts? In future we are planning to split qpid-java into 2 separate projects: qpid java broker and qpid legacy jms client. We might need parent pom project for them but I am not sure. Kind Regards, Alex [1] https://svn.apache.org/repos/asf/qpid/maven [2] https://issues.apache.org/jira/browse/QPID-6772 --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
