you could push a relocation pom to the old GAV for the next couple of
2.0.x releases and then at 2.1 stop with the relocation poms...
that would give people with the 2.0.x deps a route but you are
kind of ool for now
On 28 May 2012 23:15, Rolf Lear wrote:
> Unfortunately, there are already s
Unfortunately, there are already some 'third party' packages that depend
on jdom 2.0.1, and thus, people using the new jdom2 2.0.2 will have two
different versions of the same jar right? ... which is perhaps
worse than not having it at all ... ;-)
Rolf
On 28/05/2012 6:12 PM, Benson Margu
Publish another copy with a '2' in the artifactId?
On Mon, May 28, 2012 at 6:09 PM, Rolf Lear wrote:
> Hi all.
>
> I maintain the JDOM project, and unfortunately it seems I made a 'novice'
> error when deploying a new version of JDOM to maven-central.
>
> Thus, the situation is as follows:
> http
Hi all.
I maintain the JDOM project, and unfortunately it seems I made a
'novice' error when deploying a new version of JDOM to maven-central.
Thus, the situation is as follows:
http://search.maven.org/#browse|-1946144149
JDOM 2.x was released with a separate (new) package name for the expr
Hi
I had the same issue but with Eclipse.
I explain what solved my problem, hoping this will help next personns facing
this issue.
I configured correctly maven-compiler-plugin with source in Java 1.4.
The problem was the Java compiler configuration.
I changed Java build Path, from JRE 1.4 to JRE
The Maven team is pleased to announce the release of the Maven Plugin
Testing, version 2.0
The Maven Plugin Testing contains the necessary modules to be able to
test Maven Plugins.
http://maven.apache.org/plugin-testing/
org.apache.maven.plugin-testing
maven-plugin-testing-harnes
The Maven team is pleased to announce the release of the Maven Runtime, version
1.0-alpha-3
Maven Runtime allows introspection of Maven project metadata at runtime. Basic
artifact information or full Maven
project metadata can be obtained for all projects within a given class
loader, opti
