Re: [maven-scm-api] Looking to perform svn remote move

[Gary Gregory]

On Fri, May 18, 2018 at 8:00 PM, Hervé BOUTEMY 
wrote:

> Le vendredi 18 mai 2018, 22:36:20 CEST Rob Tompkins a écrit :
> > > On May 18, 2018, at 3:30 PM, Michael Osipov 
> wrote:
> > >
> > > Am 2018-05-17 um 15:12 schrieb Rob Tompkins:
> > > > Hello maven guys,
> > > >
> > > > Over on commons we’ve been writing our own release-plugin
> > >
> > > What is wrong with the current Maven Release Plugin and why are you
> > > writing your own whereas we could improve the current one, can't we?
> > We are trying to fit the Apache release paradigm where we are dealing
> with
> > assemblies that we don’t want to deliver to Nexus. Further we are
> > publishing the site up to our dev dist area for comparison with RC
> > validation. We could contribute it back to the release plugin, but I’m
> not
> > sure if it’s sufficiently general. Thoughts?
>
> IIUC, the "release plugin" from Commons provides 3 mojos to prepare 3
> assemblies: it does not replace "release plugin" from Maven, which
> modifies
> pom.xml to switch from -SNAPSHOT to release version then to next SNAPSHOT
>
> How is Commons release plugin used during a Commons release vs Maven
> release
> plugin?


Please see "Create the Release Candidate with the Commons Release Plugin."
here: https://commons.apache.org/releases/prepare.html

Before our plugin, you had to follow "Create the Release Candidate
Manually" (same page).

I'm not sure what is done under the covers WRT the Maven release plugin.

Do Commons use "mvn release:prepare" then "mvn release:perform", and
> the build in the release profile runs the 3 mojos to get the 3 assemblies?
>
> Because what I see in this Commons release plugin look like custom steps
> to
> add to Maven release plugin, in addition to currently provided ones: as
> Robert
> wrote, there is a WIP in Maven release plugin to document how to add new
> steps. The Maven release plugin is already organized in steps, to be
> flexible,
> but just has not documented how to add new steps.
>

It would be great to iterate with the Maven team so that we can make
releasing Commons component easier. It's a giant pain ATM IMO. Creating a
release candidate [1] is "easy" compared to what has to happens after a
successful VOTE [2]. It should be easier instead of 50 steps.

Gary

[1] https://commons.apache.org/releases/prepare.html
[2] http://commons.apache.org/releases/release.html


>
> Regards,
>
> Hervé
>
> >
> > -Rob
> >
> > > 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
>
>

Re: Problem with exec-maven-plugin

[Francois MAROT]

Hi Alex,

maybe you could paste here the output logs of the failing execution. I'd
like them to be sure I understand the problem.
Cheers

Francois



--
Sent from: http://maven.40175.n5.nabble.com/Maven-Users-f40176.html

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

Re: Accessing licenses/license as POM properties?

[Mark Raynsford]

This seems to be a bug or something not quite right with the
bnd-maven-plugin. I've filed an issue:
https://github.com/bndtools/bnd/issues/2454

Plugins like the maven-jar-plugin (and evidently the
maven-bundle-plugin) appear to do the right thing, but the
bnd-maven-plugin seems not to. Strangely, other expressions (like
${project.description}) are expanded properly, but more complex
expressions aren't.

-- 
Mark Raynsford | http://www.io7m.com



pgpFjONIzyHYR.pgp
Description: OpenPGP digital signature

Re: Accessing licenses/license as POM properties?

[Mark Raynsford]

On 2018-05-19T14:35:25 +0200
Andreas Sewe  wrote:
>
> Maybe it depends on the Maven version (here: 3.5.2)? Try to clone the
> above Github repository, do a "mvn clean verify" and check what "unzip
> -p
> bundles/com.ctrlflow.aer.client.dto/target/com.ctrlflow.aer.client.dto-2.0.2-SNAPSHOT.jar
> META-INF/MANIFEST.MF" outputs for you.

I'm on 3.5.2:

Apache Maven 3.5.2 (NON-CANONICAL_2017-10-25T13:09:52+03:00_root; 
2017-10-25T11:09:52+01:00)
Maven home: /opt/maven
Java version: 10.0.1, vendor: Oracle Corporation
Java home: /usr/lib/jvm/java-10-openjdk
Default locale: en_GB, platform encoding: UTF-8
OS name: "linux", version: "4.16.4-1-arch", arch: "amd64", family: "unix"

Your bundles have the correct manifest entries on my system:

  Bundle-License: https://www.eclipse.org/legal/epl-v10.html;description
 ="Eclipse Public License"

> Also, check what "mvn help:effective-pom" produces on your project vs.
> my project.

The effective POM for my project shows the unexpanded
${project.licenses[0]} text.

I feel like I might be running into a bug here... Going to attempt to
produce a repro case and submit an issue to the tracker.

-- 
Mark Raynsford | http://www.io7m.com



pgpEqdLJo6A61.pgp
Description: OpenPGP digital signature

Re: Accessing licenses/license as POM properties?

[Andreas Sewe]

Mark Raynsford wrote:
> Spoke a bit too soon. I'm using the bnd-maven-plugin, but I don't think
> that changes anything. I have:
> 
> 
>   biz.aQute.bnd
>   bnd-maven-plugin
>   ${io7m.bnd-maven-plugin.version}
>   
> 
>   
> 
> 
> Unfortunately, the resulting bundle manifest is:
> 
>   Bundle-Description  Contract checking  
>   Bundle-License  ${project.licenses[0].name}  
> 
> It seems that the array reference isn't being expanded. If I specify
> ${project.licenses}, I instead get:
> 
>   Bundle-License  [org.apache.maven.model.License@3eba57a7]
> 
> ... which is clearly the result of calling toString() on something
> that hasn't overridden it. Point is that the project.licenses property
> is definitely present, it's just that I'm unable to access any of the
> elements.

That is odd. I just rebuild my project [1] again and checked
MANIFEST.MF, as included in the JAR, and everything is as it should be:

> Bundle-License: https://www.eclipse.org/legal/epl-v10.html;description
>  ="Eclipse Public License"

Maybe it depends on the Maven version (here: 3.5.2)? Try to clone the
above Github repository, do a "mvn clean verify" and check what "unzip
-p
bundles/com.ctrlflow.aer.client.dto/target/com.ctrlflow.aer.client.dto-2.0.2-SNAPSHOT.jar
META-INF/MANIFEST.MF" outputs for you.

Also, check what "mvn help:effective-pom" produces on your project vs.
my project.

Hope this helps to diagnose the issue.

Best wishes,

Andreas

[1] 



signature.asc
Description: OpenPGP digital signature