RE: Netbeans Maven module with Java 9 plain module dependency does not work

[Eric Barboni]

Sorry wrong ml.

Regards
Eric

-Message d'origine-
De : Eric Barboni  
Envoyé : vendredi 12 juillet 2019 14:23
À : 'Maven Users List' 
Objet : RE: Netbeans Maven module with Java 9 plain module dependency does not 
work

Hi,

Please use the 4.2 version

org.apache.netbeans.utilities

nbm-maven-plugin

4.2

 

Jar generated by jdk>8 cannot be parsed by older version on the plugin.

 

Regards

Eric

 

De : Geertjan Wielenga  Envoyé : vendredi 12 juillet 2019 
11:25 À : Klaus Martinschitz  Cc : NetBeans 
Mailing List  Objet : Re: Netbeans Maven module with 
Java 9 plain module dependency does not work

 

Which version of NetBeans? Which JDK? Which operating system?

 

This seems to be related: https://github.com/mojohaus/nbm-maven-plugin/issues/30

 

Gj

 

On Fri, Jul 12, 2019 at 3:06 AM Klaus Martinschitz mailto:klausmartinsch...@gmail.com> > wrote:

Hello,

 

I created a very simple Netbeans Module app, containing

· The aggregator Module  (it’s called parent)

· The app module

· The branding module

· An additional Netbeans module, let’s call it X.

 

Everything works fine on compile.

 

Now, I have got a plain Java module with source level 9 (Jigsaw) containing a 
module-info.class file. Compiling works perfect.

 

However, If I add the plain Java module with  source level 9 to my X module, I 
get a compilation failure. The error is…

 

Failed to execute goal org.codehaus.mojo:nbm-maven-plugin:4.1:manifest 
(default-manifest) on project Module: Execution default-manifest of goal 
org.codehaus.mojo:nbm-maven-plugin:4.1:manifest failed.: 
IllegalArgumentException -> [Help 1]

 

To see the full stack trace of the errors, re-run Maven with the -e switch. 
Re-run Maven using the -X switch to enable full debug logging.

 

For more information about the errors and possible solutions, please read the 
following articles: [Help 1] 
http://cwiki.apache.org/confluence/display/MAVEN/PluginExecutionException

 

After correcting the problems, you can resume the build with the command   mvn 
 -rf :Module

 

Is it possible that Java 9 modules cannot be added as dependency to a Netbeans 
Maven module?

 

Thanks.

 

Regards,

Klaus

 



-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

RE: Netbeans Maven module with Java 9 plain module dependency does not work

[Eric Barboni]

Hi,

Please use the 4.2 version

org.apache.netbeans.utilities

nbm-maven-plugin

4.2

 

Jar generated by jdk>8 cannot be parsed by older version on the plugin.

 

Regards

Eric

 

De : Geertjan Wielenga  
Envoyé : vendredi 12 juillet 2019 11:25
À : Klaus Martinschitz 
Cc : NetBeans Mailing List 
Objet : Re: Netbeans Maven module with Java 9 plain module dependency does not 
work

 

Which version of NetBeans? Which JDK? Which operating system?

 

This seems to be related: https://github.com/mojohaus/nbm-maven-plugin/issues/30

 

Gj

 

On Fri, Jul 12, 2019 at 3:06 AM Klaus Martinschitz mailto:klausmartinsch...@gmail.com> > wrote:

Hello,

 

I created a very simple Netbeans Module app, containing

· The aggregator Module  (it’s called parent)

· The app module

· The branding module

· An additional Netbeans module, let’s call it X.

 

Everything works fine on compile.

 

Now, I have got a plain Java module with source level 9 (Jigsaw) containing a 
module-info.class file. Compiling works perfect.

 

However, If I add the plain Java module with  source level 9 to my X module, I 
get a compilation failure. The error is…

 

Failed to execute goal org.codehaus.mojo:nbm-maven-plugin:4.1:manifest 
(default-manifest) on project Module: Execution default-manifest of goal 
org.codehaus.mojo:nbm-maven-plugin:4.1:manifest failed.: 
IllegalArgumentException -> [Help 1]

 

To see the full stack trace of the errors, re-run Maven with the -e switch. 
Re-run Maven using the -X switch to enable full debug logging.

 

For more information about the errors and possible solutions, please read the 
following articles: [Help 1] 
http://cwiki.apache.org/confluence/display/MAVEN/PluginExecutionException

 

After correcting the problems, you can resume the build with the command   mvn 
 -rf :Module

 

Is it possible that Java 9 modules cannot be added as dependency to a Netbeans 
Maven module?

 

Thanks.

 

Regards,

Klaus

 

RE: publishing Apache Netbeans maven plugin to central

[Eric Barboni]

Hi 

@Michael
All the lib are present at http://bits.netbeans.org/maven2/
It allows via nbm-maven-plugin to use maven as the build tools to make 
application on top of Netbeans. It's an old feature present since  at least 2008

@Robert 
Thanks for the pointer.

Eric
-Message d'origine-
De : Michael Osipov <1983-01...@gmx.net> 
Envoyé : vendredi 5 octobre 2018 15:21
À : users@maven.apache.org
Objet : Re: publishing Apache Netbeans maven plugin to central

> Hi Maven folks,
> 
>  
> 
> Apache NetBeans is under incubation right know and we would like to 
> publish it to maven central.

What is the benefit having all NetBeans on Central? Those aren't usable 
libraries, but a whole package. Can't it just live in the Apache Dist area?

Michael

-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org



-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

publishing Apache Netbeans maven plugin to central

[Eric Barboni]

Hi Maven folks,

 

Apache NetBeans is under incubation right know and we would like to publish
it to maven central.

 

Apache NetBeans is built using Ant. A maven tools done by Milos Kleint at
mojohaus take the built items and populate a maven repository making a set
of file  (pom,jar and nbm). 

Tool try to get dependencies from maven central. If tool fail to find it
populate a jar of the dependencies. All this pom are without licence now. 

 

It's about 500M in size (but it will grow as more code donation are
expected). 

At the time NetBeans was at Oracle,

each release or beta were published with the following version scheme
RELEASEnnn, or RELEASEnnn-BETA

nightly build were released  as dev-SNAPSHOT and SNAPSHOT the snapshot
repository were deleted before each nightly publication to avoid hard drive
space issue.

 

 

What would be a good way to get artifacts publish to maven central? (is
Apache Archiva an option?)

What is the minimal pom.xml section to have?

 

Many thanks

 

Regards

Eric Barboni(skygo)

 

RE: Maven-Indexer 6.0 Release

[Eric Barboni]

Hi,
 Sounds like a plan for me.

-Message d'origine-
De : Tamás Cservenák [mailto:ta...@cservenak.net] 
Envoyé : jeudi 23 novembre 2017 16:14
À : Maven Users List 
Objet : Re: Maven-Indexer 6.0 Release

Hi there,

I think with this PR 6.0 should be ready to go:
https://github.com/apache/maven-indexer/pull/21

Then, we can "jump" to 7 :)
- make it java8
- consume the lucene update PR
https://github.com/apache/maven-indexer/pull/19


WDYT?


On Tue, Nov 21, 2017 at 3:13 PM Andreas Sewe < 
s...@st.informatik.tu-darmstadt.de> wrote:

> Hi,
>
> > I am "ressurecting" an old topic. I wonder if it is possible to 
> > have
> some news for 6.0 release of maven indexer.
> >
> > The old version of maven indexer make a plugin fail at runtime 
> > with
> maven 3.1.1+  (see [2]). And works well with 6.0.
>
> FWIW, I'm also quite keen on proper release of 6.0 (currently working 
> with a locally-built 6.0 snapshot).
>
> Best wishes,
>
> Andreas
>
>
>
> --
Thanks,
~t~


-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

RE: Maven-Indexer 6.0 Release

[Eric Barboni]

Hi,
 
I am "ressurecting" an old topic. I wonder if it is possible to have some 
news for 6.0 release of maven indexer.

The old version of maven indexer make a plugin fail at runtime with maven 
3.1.1+  (see [2]). And works well with 6.0.

 Kind Regards

Eric
 
[1] https://github.com/mojohaus/nb-repository-plugin
[2] https://issues.apache.org/jira/browse/MINDEXER-106
-Message d'origine-
De : Martin Todorov [mailto:carlspr...@gmail.com] 
Envoyé : lundi 29 février 2016 17:31
À : Maven Users List 
Objet : Re: Maven-Indexer 6.0 Release

Hi,

I was working on a few of the issues for the 6.0-SNAPSHOT together with Tamas.

There's still a few things to clean up before it would make sense to make a new 
release.
- There's a lot of references to Nexus*. I was working on making this more 
generic, so that there is no classes that have that.
- There was still some Plexus stuff to clean up. I believe that was related to 
the index downloading.
- Guava instead of Plexus utils needed some more work, if I recall correctly.
- Some of the dependencies need to be updated

There's still things to be done. If somebody would like to join in, we could 
finish this up quicker.

Kind regards,

Martin




On Mon, Feb 22, 2016 at 7:40 AM, Janarthanan Mohan < 
janarthanan.mo...@oracle.com> wrote:

> Hi Tamás,
>
> Thanks for the response.
>
> I see there are 3 issues mentioned as still pending for 6.0 RELEASE 
> from the link given by you.
>
> MINDEXER-24: Seems to be resolved. We can see the maven-indexer site 
> available here: http://maven.apache.org/maven-indexer
>
> MINDEXER-39: Looks like this has been fixed already (its actually 
> subtask of MINDEXER-80). And I see that latest code of MI is already 
> de-plexusized
>
> MINDEXER-80: From the comments, seems that only couple of things 
> pending here are:
>
> Polish the dependencies in the pom files.
> Use guava instead of plexus-utils.
>
> But looking at commit history shows that these are actually fixed and 
> merged to master. Do we have any pending thing for this issue. If 
> those are minor, can we cut off a release branch and fix the minor 
> issues in next minor release (6.1 or something) rather than depriving 
> users of some nice features you and other have merged in the last 
> couple of years.
>
> Thanks,
> Jana
>
>
>
> --
> View this message in context:
> http://maven.40175.n5.nabble.com/Maven-Indexer-6-0-Release-tp5862615p5
> 862780.html Sent from the Maven - Users mailing list archive at 
> Nabble.com.
>
> -
> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
> For additional commands, e-mail: users-h...@maven.apache.org
>
>


-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

New maven site and doxia with custom velocity doxia

[Eric Barboni]

Hi,

  I had a web site with custom template using custom velocity tools. Using
an approach equivalent to (reflow-velocity-tools [1]). After using the new
maven site (3.5) and maven doxia (1.7) the tools is no more detected.

 

Is there a workaround or is this option gone.

 

[1] https://github.com/andriusvelykis/reflow-maven-skin

 

Best Regards

Eric 

 

 

RE: [VOTE] Change project logo and adopt owl as mascot

[Eric Barboni]

+1

Owl the best


-Message d'origine-
De : Stephen Connolly [mailto:stephen.alan.conno...@gmail.com] 
Envoyé : mercredi 3 décembre 2014 12:43
À : Maven Developers List; Maven Users List
Objet : Re: [VOTE] Change project logo and adopt owl as mascot

Any last votes?

You have 17 minutes!!!

On 1 December 2014 at 22:55, Hervé BOUTEMY herve.bout...@free.fr wrote:

 +1

 Regards,

 Hervé

 Le lundi 1 décembre 2014 07:54:56 Baptiste Mathus a écrit :
  +1.
 
  Though I quite also like the comment about having some form of M on 
  the chest (say like a superman S), but I'm late to the train here.
 
  Le 28 nov. 2014 10:38, Dennis Lundberg denn...@apache.org a écrit :
   +1
  
   On Tue, Nov 25, 2014 at 11:57 AM, Stephen Connolly
  
   stephen.alan.conno...@gmail.com wrote:
For anyone who has been living under a rock, here is the 
background
   
Background
=
   
I think everyone can agree that the site needs a reorganisation 
and a rewrite. Users cannot find what they need, and the end 
result is that people keep on abusing maven rather than having maven 
help them.
   
Try as I might, I have been unable to motivate myself to do the 
reorganisation with the current dated look and feel of the 
site... I
 am
  
   not
  
saying that picking a new logo and selecting a mascot will 
result in
  
   making
  
progress, but it can't hurt and I believe it will help
   
Proposed changes
===
   
1. Change the logo font to Alte Haas Grotesk Bold with italics
 applied
by
Inkscape
2. Change the highlighted letter from 'a' to 'v' and replace the 
v
 with
  
   two
  
Apache Feathers
3. Adopt the (currently unnamed) owl as our mascot
   
Here is a link to the font:
   
http://www.dafont.com/alte-haas-grotesk.font
  
Here is a large version of the owl and the logo:
  
 http://people.apache.org/~stephenc/maven-logo-contest/maven-owl-final-
 larg
   e.png
A regular version of the own and the logo, e.g. a size suitable 
for
 use
  
   in
  
the top of the standard maven sites:
  
 http://people.apache.org/~stephenc/maven-logo-contest/maven-owl-final.
 png
  
(Note that in all likelihood, the mascot would probably end up 
on the
  
   other
  
side of the title bar from the logo... and that is IF the mascot
 ends up
  
   on
  
the title bar)
   
Here is both of those rendered in a site (as it can be helpful 
to see the graphics adjacent to text)
  
  
 http://people.apache.org/~stephenc/maven-logo-contest/maven-owl-final-
 cont
   ext.png
Logo Rational
===
  
If we do some searches for the Maven logo:
  
 https://www.google.com/search?site=imghptbm=ischq=maven+logooq=mave
 n+lo
   go
  
  
  
 http://www.bing.com/images/search?q=maven+logogo=Submitqs=nform=QBL
 Hsc
   ope=imagespq=maven+logo
Our current logo, with a single highlighted letter stands out 
quite
 well
from the other maven logos, so keeping a highlighted letter 
and an
  
   italic
  
rendered font maintains continuity with our current logo.
   
By changing the highlighted letter to the `v` and by using two 
Apache feathers to create the `v`, we connect our logo back to 
Apache... we
 are
Apache Maven after all.
   
The `v` is also the common short term for version (e.g.v3 is 
short
 for
version 3). Apache Maven puts a lot of emphasis on versions of
  
   dependencies
  
and plugins... you could say that versions are very important to
 Maven.
   
The colours of the feather were changed to solid colours to 
match the owl mascot's scarf, beak and eyebrows
   
Voting rules
=
   
Anyone who is subscribed to the dev or users list is eligible to
 vote.
   
If you vote multiple times, only your final vote will be counted.
   
The vote will be open until 1:00pm GMT on Wed 3rd Dec 2014
   
The vote is for all three changes as one single change. Partial 
votes
  
   (e.g.
  
for the logo but not the mascot, or vice-versa) will not be counted.
   
I, as the caller of the vote, reserve the right to cancel the 
vote if
  
   this
  
vote is putting the harmony of the community at risk.
   
If a majority of the PMC believe that this vote is putting the
 harmony
of
the community at risk, then the PMC may cancel this vote (though 
if
 even
  
   a
  
small minority of the PMC were of that belief, I will more than
 likely
  
   have
  
cancelled the vote before the PMC would need to decide... I'm 
just
  
   stating
  
this FTR)
   
The decision will be a simple majority, there will be no special 
veto powers.
   
+1: [ ] Change the logo to the proposed logo and adopt the owl 
+as
project
mascot
0: [ ] No opinion
-1: [ ] No change
   
Please only respond with +1, 0 or -1. If you want to discuss the 
proposed changes 

RE: Maven with JDK 7

[Eric Barboni]

Hi, 

You may use -Djava.net.preferIPv4Stack=true for non netbeans executed jvm
or -J-Djava.net.preferIPv4Stack=true  in the netbeans_default_options in 
/etc/netbeans.conf file to 
be able  to forec  jdk 7 to use  ipv4

Eric

-Message d'origine-
De : Markku Saarela [mailto:markku.saar...@pp6.inet.fi] 
Envoyé : mercredi 27 juin 2012 14:27
À : users@maven.apache.org
Objet : Re: Maven with JDK 7

Hi,

Java 7 use IPv6 (not IPv4) if OS supports it. So if you firewall restricts IPv6 
then you got behavior you describe. Also Nexus running on Java 7 failed to 
connect and app servers etc if firewall does not allow
IPv6 communication.

Markku

On 27.6.2012 15:18, Delaney, Andy wrote:

 Hi All

 I’m working on a JDK 7 project and am trying to use maven to build the 
 project.   However, when I try to run the maven bat under Java 7 it 
 fails to download any dependencies – when I switch back to Java 6 it 
 downloads them just fine but of course can’t compile my java 7 sources.

 Looking through the forums the only advice I can get is to revert to 
 Java 6 – this isn’t an option as I need to compile Java 7 sources.

 Has anyone come across this problem or understand why it is happening 
 – presumably there is a change in the JDK and the way it handles 
 socket connections?

 The underlying exception is a timeout exception which would lead me 
 think this was something to do with proxies or firewalls but I have 
 tried switching the firewall off and as it runs OK under JDK 6 so I 
 don’t think that’s it.

 Caused by: java.net.ConnectException: Connection timed out: connect

 at java.net.DualStackPlainSocketImpl.connect0(Native Method)

 at
 java.net.DualStackPlainSocketImpl.socketConnect(DualStackPlainSocketIm
 pl.java:69)

 at
 java.net.AbstractPlainSocketImpl.doConnect(AbstractPlainSocketImpl.jav
 a:339)

 at
 java.net.AbstractPlainSocketImpl.connectToAddress(AbstractPlainSocketI
 mpl.java:200)

 at
 java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:
 182)

 at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:157)

 at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:391)

 at java.net.Socket.connect(Socket.java:579)

 at
 org.apache.maven.wagon.providers.http.httpclient.conn.scheme.PlainSock
 etFactory.connectSocket(PlainSocketFactory.java:123)

 at
 org.apache.maven.wagon.providers.http.httpclient.impl.conn.DefaultClie
 ntConnectionOperator.openConnection(DefaultClientConnectionOperator.ja
 va:148)

 ... 16 more

 I would appreciate any help you might be able to offer me.

 Many thanks

 Andy

 Tullett Prebon - Best Data Provider (Broker) - Inside Market Data 
 Awards 2012

 --
 -

 The information contained in this email is confidential and may also 
 contain privileged information. Sender does not waive confidentiality 
 or legal privilege. If you are not the intended recipient please 
 notify the sender immediately; you should not retain this message or 
 disclose its content to anyone.

 Internet communications are not secure or error free and the sender 
 does not accept any liability for the content of the email. Although 
 emails are routinely screened for viruses, the sender does not accept 
 responsibility for any damage caused. Replies to this email may be 
 monitored.

 For more information about the Tullett Prebon group of companies 
 please visit the following web site: _www.tullettprebon.com_

 --
 -





-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

Multiple versions distribution best practice ?

[Eric Barboni]

Hi
I was reading documentation dealing with version and  it says that with 
dist plugin I can build each of the version I've tagged. for example:

currentVersion1.0/currentVersion


versions
   version
 id1.0/id
 name1.0/name
 tagPET-1.0/tag
   /version
   version
 id1.5/id
 name1.5/name
 tagHEAD/tag
   /version
 /versions
Did I miss something ? As anybody and idea.
Best Regards
Eric

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

JCoverage and Junit do not give same test result

[Eric Barboni]

Hi,
 I'm using JCoverage plugin and Junit plugin in the same project.
  Junit report no failure and no error
  Jcoverage report an error with the same testcase.
I've got a java.lang.VerifyError (Illegal constant pool index)
I'm using the following properties:
maven.test.failure.ignore=true
maven.junit.fork=yes
maven.junit.jvmargs=-Djava.awt.headless=true
maven.compile.source=1.5
maven.compile.target=1.5
maven.jcoverage.junit.fork=yes
Has anybody an idea of what happen?
Best Regards
Eric

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]