Re: disabling default plugin from phase?

[Mark Prins]

On 04-12-15 02:58, Martin Gainty wrote:

was asked by a local resource to look into resurrecting flex-mojos for a local 
company

Thanks to Jeff, Mirko and Adrien I was able to exec thru all the phases to make 
flexmojos operational ..but..
I am disturbed by EOL notice from code.google.com to take place at end of 
2015http://code.google.com/p/flex-mojos/
Remembering that codehaus projects have been re-provisioned  from codehaus to 
apache servers this year


i'd just hit the "Export to Github" button on 
https://code.google.com/archive/p/flex-mojos/ and switch over



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

RE: disabling default plugin from phase?

[Martin Gainty]

 good for SCM access
how about site distro?
it would seem *logical* to aggregate all of the flexmojos src/doc/site info for 
flex mojos under Apache-flex?
thanks mark
Martin 
__ 


> Subject: Re: disabling default plugin from phase?
> To: users@maven.apache.org
> From: mc.pr...@gmail.com
> Date: Mon, 7 Dec 2015 16:27:52 +0100
> 
> On 04-12-15 02:58, Martin Gainty wrote:
> > was asked by a local resource to look into resurrecting flex-mojos for a 
> > local company
> >
> > Thanks to Jeff, Mirko and Adrien I was able to exec thru all the phases to 
> > make flexmojos operational ..but..
> > I am disturbed by EOL notice from code.google.com to take place at end of 
> > 2015http://code.google.com/p/flex-mojos/
> > Remembering that codehaus projects have been re-provisioned  from codehaus 
> > to apache servers this year
> 
> i'd just hit the "Export to Github" button on 
> https://code.google.com/archive/p/flex-mojos/ and switch over
> 
> 
> -
> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
> For additional commands, e-mail: users-h...@maven.apache.org
> 
  

how do i specify additional wagon plugins in the project pom to build deps when they don't yet exist in built form?

[james northrup]

I would like to intercepts maven repo requests and builds the ones
that fit a certain pattern of buildable SCM repos, specifically using
git[hub] repositories.

what pom options exist to control wagon so that a similar solution can
be added to a parent pom to utilize plugin to build or exec when built
dependencies are not yet installed in specified repositories.

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

Re: [rpm-maven-plugin] how to control the name under which rpm is stored in m2 repository?

[Karl Heinz Marbaise]

Hi Steve,

simply answer to this: It is not possible...

Long answer: Maven repositories dependending on an appropriate naming 
schema to find artifacts / versions etc. If you change that the whole 
system will not work at all..


So the name which is stored within a maven repository can't be changed.

Kind regards
Karl Heinz Marbaise

On 12/7/15 7:44 PM, Steve Cohen wrote:

Our organization has a convention for naming rpms. Typically, the rpm
will have a shorter base name than the Maven project. There is also a
convention around how releases are named. So we want a name
like|${shortname}-${project.version}-${release}.noarch.rpm|.

I want to build such rpms using the rpm-maven-plugin rather than older
nmake technology.

And this is easily accomplished using the plugin's parameters. The rpm
generated in the target directory has the desired name.

However, when|mvn install|installs this rpm into the maven repository,
it insists on storing it the "maven
way":|${project.artifactId}-${project.version}.rpm|

I want the rpm stored in the standard maven repository directory using
the name that is initially created on package.

I also tried using the maven-install-plugin (install-file goal) and did
not get the results I was after.

How may I accomplish this?



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

Re: how do i specify additional wagon plugins in the project pom to build deps when they don't yet exist in built form?

[Karl Heinz Marbaise]

Hi,

On 12/7/15 8:15 PM, james northrup wrote:

I would like to intercepts maven repo requests and builds the ones
that fit a certain pattern of buildable SCM repos, specifically using
git[hub] repositories.


Maven is based on binary artifacts and NOT on source artifacts...



what pom options exist to control wagon so that a similar solution can
be added to a parent pom to utilize plugin to build or exec when built
dependencies are not yet installed in specified repositories.


By default there does not exist such an machanism...for good reasons...

Why you might can do use a EventSpy to intercept the repository request 
so you might can create an Maven extension which could handle that


But you might take a look to this:

https://github.com/l2x6/srcdeps-maven-plugin

but from my point of view it will break all the advantages Maven 
has...which means you don't need to rebuild everything everytime...


Kind regards
Karl Heinz Marbaise

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

Re: [rpm-maven-plugin] how to control the name under which rpm is stored in m2 repository?

[Graham Leggett]

On 07 Dec 2015, at 8:44 PM, Steve Cohen  wrote:

> Our organization has a convention for naming rpms. Typically, the rpm will 
> have a shorter base name than the Maven project. There is also a convention 
> around how releases are named. So we want a name 
> like|${shortname}-${project.version}-${release}.noarch.rpm|.
> 
> I want to build such rpms using the rpm-maven-plugin rather than older nmake 
> technology.
> 
> And this is easily accomplished using the plugin's parameters. The rpm 
> generated in the target directory has the desired name.
> 
> However, when|mvn install|installs this rpm into the maven repository, it 
> insists on storing it the "maven 
> way":|${project.artifactId}-${project.version}.rpm|
> 
> I want the rpm stored in the standard maven repository directory using the 
> name that is initially created on package.
> 
> I also tried using the maven-install-plugin (install-file goal) and did not 
> get the results I was after.
> 
> How may I accomplish this?

You don’t change the name of a maven artefact, maven depends on this format and 
you break maven if you try and change it.

Turns out yum is also very particular about naming formats, and is different to 
maven. What we’ve done to solve this is to create hard links from the entry in 
the maven repo to the entry in the yum repo, introspecting the RPM to work out 
what the name should be, like this:

RPMDIST=`/bin/rpm -q --qf "%{DISTRIBUTION}\n" -p "${FILE}" | tr -cd 
[:alnum:]`
RPMPATH=${YUMPATH}/${REPO}/${RPMDIST}/`/bin/rpm -q --qf "%{ARCH}\n" -p 
"${FILE}"`
RPMFILE=${RPMPATH}/`/bin/rpm -q --qf 
'%{NAME}-%{VERSION}-%{RELEASE}.%{DISTRIBUTION}.%{ARCH}.rpm\n' -p "${FILE}”`

To be even more specific, we do this automatically when artefacts are published 
to our webdav server. We hang the following 
script off Apache httpd’s reiiable piped logging feature which auto-processes 
the file as soon as an upload is complete:

  # reindex the yum repo on rpm PUT
  CustomLog "|/usr/sbin/reindex-yum-filter-repo-greenhouse 
/var/lib/httpd-repo-greenhouse/web-docs/maven2 
/var/lib/httpd-repo-greenhouse/web-docs/yum" "%m %f"

Script is as follows:

#!/bin/bash

# Filter logfile lines from httpd-dev
#
# We are only interested in PUT requests, and we only consider the filename
# resolved by httpd, so we don't use any untainted input in this script.
#
# We extract the DISTRIBUTION (example: el6) and ARCH (example: x86_64, noarch)
# fields to determine the yum repo to link the RPM to.

MAVENPATH="$1"
YUMPATH="$2"
LOCK="/tmp/$0.lock"

trap "rm -f ${LOCK}" EXIT

while read LINE
do
  if [ "x${LINE:0:4}" == "xPUT " ]; then
FILE=`/usr/bin/readlink -f "${LINE:4}"`
if [[ "${FILE}" =~ ^${MAVENPATH}/.*[.]rpm$ ]]; then
  if [[ "${FILE}" =~ SNAPSHOT ]]; then
RPMREPO="snapshot"
  else
RPMREPO="master greenhouse"
  fi
  touch "${LOCK}"
  for REPO in ${RPMREPO}; do
RPMDIST=`/bin/rpm -q --qf "%{DISTRIBUTION}\n" -p "${FILE}" | tr -cd 
[:alnum:]`
RPMPATH=${YUMPATH}/${REPO}/${RPMDIST}/`/bin/rpm -q --qf "%{ARCH}\n" -p 
"${FILE}"`
RPMFILE=${RPMPATH}/`/bin/rpm -q --qf 
'%{NAME}-%{VERSION}-%{RELEASE}.%{DISTRIBUTION}.%{ARCH}.rpm\n' -p "${FILE}"`
if [ ! -f "${RPMFILE}" ]; then
  /bin/rpm -q --quiet -p "${FILE}" && \
  /bin/mkdir -p "${RPMPATH}" && \
  /bin/ln "${FILE}" "${RPMFILE}" && \
  /usr/bin/createrepo -q --update --checkts 
"${YUMPATH}/${REPO}/${RPMDIST}"
fi
  done
  rm -f "${LOCK}"
fi
  fi
done

Regards,
Graham
—


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

Re: how do i specify additional wagon plugins in the project pom to build deps when they don't yet exist in built form?

[james northrup]

thanks, i doubt a new wagon option would subtract from the maven build
experience if broken deps are resolved back to thier source

https://jitpack.io/#l2x6/srcdeps-maven-plugin/0.0.11 does it as
transparent SAAS.

On Mon, Dec 7, 2015 at 11:58 AM, Karl Heinz Marbaise  wrote:
> Hi,
>
> On 12/7/15 8:15 PM, james northrup wrote:
>>
>> I would like to intercepts maven repo requests and builds the ones
>> that fit a certain pattern of buildable SCM repos, specifically using
>> git[hub] repositories.
>
>
> Maven is based on binary artifacts and NOT on source artifacts...
>
>>
>> what pom options exist to control wagon so that a similar solution can
>> be added to a parent pom to utilize plugin to build or exec when built
>> dependencies are not yet installed in specified repositories.
>
>
> By default there does not exist such an machanism...for good reasons...
>
> Why you might can do use a EventSpy to intercept the repository request so
> you might can create an Maven extension which could handle that
>
> But you might take a look to this:
>
> https://github.com/l2x6/srcdeps-maven-plugin
>
> but from my point of view it will break all the advantages Maven has...which
> means you don't need to rebuild everything everytime...
>
> Kind regards
> Karl Heinz Marbaise
>
> -
> 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: [rpm-maven-plugin] how to control the name under which rpm is stored in m2 repository?

[Steve Cohen]

Actually, I found a way.  If I am willing to let my "short name" become 
the archiveId, (and thus live with the rpms in a different location), 
the following is possible with the maven-install-plugin, after packaging 
with the rpm-maven-plugin:




org.apache.maven.plugins

maven-install-plugin

2.5.2





install-rpm



install-file



install



${project.build.directory}/rpm/${rpm.name}/RPMS/noarch/${rpm.name}-${project.version}-${rpm.release}.noarch.rpm

${project.groupId}

${rpm.name}

${project.version}-${rpm.release}

noarch

rpm










On 12/07/2015 01:54 PM, Karl Heinz Marbaise wrote:

Hi Steve,

simply answer to this: It is not possible...

Long answer: Maven repositories dependending on an appropriate naming 
schema to find artifacts / versions etc. If you change that the whole 
system will not work at all..


So the name which is stored within a maven repository can't be changed.

Kind regards
Karl Heinz Marbaise

On 12/7/15 7:44 PM, Steve Cohen wrote:

Our organization has a convention for naming rpms. Typically, the rpm
will have a shorter base name than the Maven project. There is also a
convention around how releases are named. So we want a name
like|${shortname}-${project.version}-${release}.noarch.rpm|.

I want to build such rpms using the rpm-maven-plugin rather than older
nmake technology.

And this is easily accomplished using the plugin's parameters. The rpm
generated in the target directory has the desired name.

However, when|mvn install|installs this rpm into the maven repository,
it insists on storing it the "maven
way":|${project.artifactId}-${project.version}.rpm|

I want the rpm stored in the standard maven repository directory using
the name that is initially created on package.

I also tried using the maven-install-plugin (install-file goal) and did
not get the results I was after.

How may I accomplish this?



-
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: [rpm-maven-plugin] how to control the name under which rpm is stored in m2 repository?

[Steve Cohen]

Aargh!  Email formattting!

  org.apache.maven.plugins
  maven-install-plugin
  2.5.2
  

  install-rpm
  
install-file
  
  install
  

${project.build.directory}/rpm/${rpm.name}/RPMS/noarch/${rpm.name}-${project.version}-${rpm.release}.noarch.rpm 


${project.groupId}
${rpm.name}
${project.version}-${rpm.release}
noarch
rpm
  

  




On 12/07/2015 02:55 PM, Steve Cohen wrote:

Actually, I found a way.  If I am willing to let my "short name" become
the archiveId, (and thus live with the rpms in a different location),
the following is possible with the maven-install-plugin, after packaging
with the rpm-maven-plugin:



org.apache.maven.plugins

maven-install-plugin

2.5.2

 



 install-rpm

 

install-file

 

install

 

${project.build.directory}/rpm/${rpm.name}/RPMS/noarch/${rpm.name}-${project.version}-${rpm.release}.noarch.rpm


${project.groupId}

${rpm.name}

${project.version}-${rpm.release}

noarch

rpm

 



 




On 12/07/2015 01:54 PM, Karl Heinz Marbaise wrote:

Hi Steve,

simply answer to this: It is not possible...

Long answer: Maven repositories dependending on an appropriate naming
schema to find artifacts / versions etc. If you change that the whole
system will not work at all..

So the name which is stored within a maven repository can't be changed.

Kind regards
Karl Heinz Marbaise

On 12/7/15 7:44 PM, Steve Cohen wrote:

Our organization has a convention for naming rpms. Typically, the rpm
will have a shorter base name than the Maven project. There is also a
convention around how releases are named. So we want a name
like|${shortname}-${project.version}-${release}.noarch.rpm|.

I want to build such rpms using the rpm-maven-plugin rather than older
nmake technology.

And this is easily accomplished using the plugin's parameters. The rpm
generated in the target directory has the desired name.

However, when|mvn install|installs this rpm into the maven repository,
it insists on storing it the "maven
way":|${project.artifactId}-${project.version}.rpm|

I want the rpm stored in the standard maven repository directory using
the name that is initially created on package.

I also tried using the maven-install-plugin (install-file goal) and did
not get the results I was after.

How may I accomplish this?



-
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

[rpm-maven-plugin] Howto set directory mode of a mapping directory which has files?

[Steve Cohen]

Maybe I'm missing something, but there seems to be a hole in the logic 
of the rpm-maven-plugin mappings, and

the way file permissions are created.

Looking at the official documentation, 
http://www.mojohaus.org/rpm-maven-plugin/map-params.html, I see



 filemode(*recommended*)

This is UNIX permissions (file mode) to assign to the files when 
installed. This value consists of three octal digits representing the 
access for the owner, the group, and the world. Each digit represents 
the access allowed and is the sum of 4 for read, 2 for write, and 1 for 
execute. A common value to use is "644" which provides the owner 
read/write access and read-only access to everyone else. For more 
information on this subject, readFile Security 
, section 3.4 
of the Introduction to Linux maintained by the Linux Documentation 
Project. If not specified, the files retain the filemode assigned to 
them when copied to the RPM work area.


If none of the file attributes (filemode, username, and groupname) are 
populated, the defaults (defaultFileMode 
,defaultUsername 
,defaultGroupname 
, 
anddefaultDirmode 
) 
will be used.



 username(*recommended*)

This is the UNIX username to assign to the files when installed. If the 
named user does not exist when the package is installed, the 
userrootwill be used. If not specified, the files will be owned by the 
user used to create the package.


If none of the file attributes (filemode, username, and groupname) are 
populated, the defaults (defaultFileMode 
,defaultUsername 
,defaultGroupname 
, 
anddefaultDirmode 
) 
will be used.



 groupname(*recommended*)

This is the UNIX groupname to assign to the files when installed. If the 
named group does not exist when the package is installed, the 
grouprootwill be used. If not specified, the files will be owned by the 
group used to create the package.


If none of the file attributes (filemode, username, and groupname) are 
populated, the defaults (defaultFileMode 
,defaultUsername 
,defaultGroupname 
, 
anddefaultDirmode 
) 
will be used.



But there is no dirmode parameter on the individual mapping.  So, if I 
set a filemode of 644 on a file mapping, its directory is created with 
644 permissions, and I don't see how with these rules to get around 
that, other than to avoid the use of filemode, username, and groupname 
on mappings, and go with the defaults, which would probably be adequate 
in most cases.  Given this sort of logic and given that mappings require 
a directory to be specified, shouldn't there be a dirmode parameter for 
mappings?  Or is there such a a parameter and this is just a 
documentation error?


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

[rpm-maven-plugin] how to control the name under which rpm is stored in m2 repository?

[Steve Cohen]

Our organization has a convention for naming rpms. Typically, the rpm 
will have a shorter base name than the Maven project. There is also a 
convention around how releases are named. So we want a name 
like|${shortname}-${project.version}-${release}.noarch.rpm|.


I want to build such rpms using the rpm-maven-plugin rather than older 
nmake technology.


And this is easily accomplished using the plugin's parameters. The rpm 
generated in the target directory has the desired name.


However, when|mvn install|installs this rpm into the maven repository, 
it insists on storing it the "maven 
way":|${project.artifactId}-${project.version}.rpm|


I want the rpm stored in the standard maven repository directory using 
the name that is initially created on package.


I also tried using the maven-install-plugin (install-file goal) and did 
not get the results I was after.


How may I accomplish this?


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