> What stops us developing on Java 8?
> Maven project stops us.
I think this deserves some clearance, because I have a different opinion on
this.
It is quite natural that plugins start picking up and requiring a more recent
version of Java before Maven does.
If there's a good reason to move forw
What stops us developing on Java 8?
Maven project stops us.
We wanted to use Java 7 and not higher. Therefore reworking the little code
with removed dom4j keeps javac still on java7 and we would not have a
problem when dom4j moves to java9+ because of non-applicable CVEs. We can
use Java XML Api in
Mkay...
but in general, the (any) plugin dependency would load at "build time"
(java8) to produce code that would run at "runtime" (java7).
Or why would you need to load a plugin dependency in runtime/target JVM?
T
On Tue, Jun 4, 2019 at 7:17 PM Elliotte Rusty Harold
wrote:
> Java 8 uses a dif
Java 8 uses a different major version number in the .class file than
Java 7. Generally a Java 8 .class file can't be loaded into a Java 7
VM. In this case, I think dom4j would have to compile for Java 7 for
the dom4j.jar to load into Java 7.
On Tue, Jun 4, 2019 at 12:32 PM Tamás Cservenák wrote:
Just wondering: what stops you developing on more modern java, and
targeting older java? Or in other words, why is using target java a must on
development? Just curious.
Ps: sry for jumping the thread
On Mon, Jun 3, 2019, 16:48 Elliotte Rusty Harold wrote:
> I know there are plenty of places at
FYI, I took a look at the code and found it is already using both
dom4j AND JDOM, even in the same class:
https://github.com/apache/maven-archetype/blob/0fd806f773354ec62c8eb40f624d78a218815506/archetype-common/src/main/java/org/apache/maven/archetype/common/DefaultPomManager.java
This is depend
Yep
I going to merge the upgrade patch as soon as I am back from vacation
https://github.com/apache/maven-archetype/pull/28
Enrico
Il mar 4 giu 2019, 11:49 Tibor Digana ha scritto:
> Sylwester, removing dom4j and substituting by Java XML API would be the
> best choice.
> Pls then inform the gu
+1
On Tue, 28 May 2019, 21:54 Robert Scholte, wrote:
> Hi,
>
> The Apache Maven project consist of about 100 (sub)projects. Due to the
> small number of volunteers and the huge amount of code to maintain we're
> missing enough space to make real progress on all these projects, including
> our am
Sylwester, removing dom4j and substituting by Java XML API would be the
best choice.
Pls then inform the guys in
https://github.com/apache/maven-archetype/pull/28 because I think they are
handling it in parallel with you.
Cheers
Tibor
On Tue, Jun 4, 2019 at 8:46 AM Sylwester Lachiewicz
wrote:
>
