Hi all!

I have currently the problem that I am unable to build the installers of
ApacheDS 1.5.

I have checked out

https://svn.apache.org/repos/asf/di...th-dependencies

and I am able to perform a "mvn install" on this level.

But if I change directory  to apacheds/server-installers and try "mvn
install" I get this

[INFO] Scanning for projects...
[INFO]
-------------------------------------------------------------------------
---
[INFO] Building ApacheDS Server Installers
[INFO]    task-segment: [install]
[INFO]
-------------------------------------------------------------------------
---
[INFO]
------------------------------------------------------------------------
[ERROR] BUILD ERROR
[INFO]
------------------------------------------------------------------------
[INFO] The plugin 'org.apache.maven.plugins:maven-resources-plugin' does
not exist or no valid version could be found
[INFO]
------------------------------------------------------------------------
[INFO] For more information, run Maven with the -e switch
[INFO]
------------------------------------------------------------------------
[INFO] Total time: < 1 second
[INFO] Finished at: Mon May 21 11:04:03 CEST 2007
[INFO] Final Memory: 1M/3M
[INFO]
------------------------------------------------------------------------

A "mvn clean" does not help on any level (runs successfully, but error
persists).

Any help is appreciated.
Thanks in advance,
Stefan

[ Post a follow-up to this message ]

Hmmmm...

I just have tested it :
svn up
mvn clean install on root
cd apacheds/server-installers
mvn clean install

no pb at all...

Have you tried to remove completly  your .m2 repository before running the
build ?

Emmanuel

On 5/21/07, Stefan Zoerner <stefan-EQq9qWhC7IA@public.gmane.org> wrote:
>
> Hi all!
>
> I have currently the problem that I am unable to build the installers of
>   ApacheDS 1.5.
>
> I have checked out
>
>
> [url]https://svn.apache.org/repos/asf/directory/apacheds/trunk-with-dependencies[/url
]
>
> and I am able to perform a "mvn install" on this level.
>
> But if I change directory  to apacheds/server-installers and try "mvn
> install" I get this
>
> [INFO] Scanning for projects...
> [INFO]
> -------------------------------------------------------------------------
> ---
> [INFO] Building ApacheDS Server Installers
> [INFO]    task-segment: [install]
> [INFO]
> -------------------------------------------------------------------------
> ---
> [INFO]
> ------------------------------------------------------------------------
> [ERROR] BUILD ERROR
> [INFO]
> ------------------------------------------------------------------------
> [INFO] The plugin 'org.apache.maven.plugins:maven-resources-plugin' do
es
> not exist or no valid version could be found
> [INFO]
> ------------------------------------------------------------------------
> [INFO] For more information, run Maven with the -e switch
> [INFO]
> ------------------------------------------------------------------------
> [INFO] Total time: < 1 second
> [INFO] Finished at: Mon May 21 11:04:03 CEST 2007
> [INFO] Final Memory: 1M/3M
> [INFO]
> ------------------------------------------------------------------------
>
> A "mvn clean" does not help on any level (runs successfully, but error
> persists).
>
> Any help is appreciated.
> Thanks in advance,
>      Stefan
>
>


-- 
Regards,
Cordialement,
Emmanuel Lécharny
www.iktek.com

[ Post a follow-up to this message ]

Hi Stefan,

I have tested it again after having removed the repo, and still working ...

On 5/21/07, Emmanuel Lecharny <elecharny-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote:[vbc
ol=seagreen]
>
> Hmmmm...
>
> I just have tested it :
> svn up
> mvn clean install on root
> cd apacheds/server-installers
> mvn clean install
>
> no pb at all...
>
> Have you tried to remove completly  your .m2 repository before running the
> build ?
>
> Emmanuel
>
> On 5/21/07, Stefan Zoerner <stefan-EQq9qWhC7IA@public.gmane.org> wrote: 
>
>
> --
> Regards,
> Cordialement,
> Emmanuel Lécharny
> www.iktek.com[/vbcol]




-- 
Regards,
Cordialement,
Emmanuel Lécharny
www.iktek.com

[ Post a follow-up to this message ]

Emmanuel Lecharny wrote:[vbcol=seagreen]
> I have tested it again after having removed the repo, and still working ...[/vbcol
]

Hi Emmanuel,

I have removed the repo from my machine, rebuilt it all and you are
right: I just came back from lunch and now I have fresh installers.

Thanks for your help,
Stefan

[ Post a follow-up to this message ]

Ahhh the unpredictability of Maven strikes again!

Alex

On 5/21/07, Stefan Zoerner <stefan-EQq9qWhC7IA@public.gmane.org> wrote:
>
> Emmanuel Lecharny wrote: 
> ...
>
> Hi Emmanuel,
>
> I have removed the repo from my machine, rebuilt it all and you are
> right: I just came back from lunch and now I have fresh installers.
>
> Thanks for your help,
>      Stefan
>
>

[ Post a follow-up to this message ]

Do you guys think that these problems are from having the SNAPSHOT repos
(regular maven repo and plugin repo) in the maven repo stack?  I am
basically in the habit of disabling the SNAPSHOT repos in any project I
build because it does stuff like this.  And yes I always disable the
SNAPSHOT repo in ApacheDS pom as well  :-)

Its always been in the back of my mind to ask why it is enabled, but I
figured that it allowed someone to build part of the SVN project without
building the entire thing or something along those lines.

Chris

On 5/21/07, Alex Karasulu <akarasulu-1oDqGaOF3Lkdnm+yROfE0A@public.gmane.org> wrote:
>
> Ahhh the unpredictability of Maven strikes again!
>
> Alex
>
> On 5/21/07, Stefan Zoerner <stefan-EQq9qWhC7IA@public.gmane.org> wrote: 
>

[ Post a follow-up to this message ]

I think this was due not to the SNAPSHOT repos but to the fact that we do
not use
a specific revision for all the plugins involved.

If we disable the SNAPSHOT repos there will be other negative effects.  For
example
when we are on a SNAPSHOT like say 1.5.1-SNAPSHOT then the snapshot jars are

deployed to the apache snapshot repo.  If a user checks out the apacheds
trunk and
tries to build that instead of building the svn area with the dependent
projects then
those snapshots from shared and daemon will not be resolved.  Even worse if
a user
checks out apacheds/trunk/server-installers and tries to build that then it
will fail if
the SNAPSHOT repos are not visible.

I think we just have to make sure we assign a specific revision to all the
plugins we
use instead of not including a revision for a plugin.  This will prevent the
use of
SNAPSHOT plugins I hope.

There is also a pluginManagement section in the pom that we need to populate
so
we lock all plugins to a specific revision instead of allowing the use of
SNAPSHOTs.

Alex

On 5/21/07, Chris Custine <chris.custine-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote:[vbc
ol=seagreen]
>
> Do you guys think that these problems are from having the SNAPSHOT repos
> (regular maven repo and plugin repo) in the maven repo stack?  I am
> basically in the habit of disabling the SNAPSHOT repos in any project I
> build because it does stuff like this.  And yes I always disable the
> SNAPSHOT repo in ApacheDS pom as well  :-)
>
> Its always been in the back of my mind to ask why it is enabled, but I
> figured that it allowed someone to build part of the SVN project without
> building the entire thing or something along those lines.
>
> Chris
>
> On 5/21/07, Alex Karasulu <akarasulu-1oDqGaOF3Lkdnm+yROfE0A@public.gmane.o
rg> wrote: 
>[/vbcol]

[ Post a follow-up to this message ]

We should never use SNAPSHOT of any external dependency, this is the perfect
way to shooting us in the foot. But for internal project like shared, etc,
we must use SNAPSHOT...

On 5/21/07, Chris Custine <chris.custine-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote:[vbc
ol=seagreen]
>
> Do you guys think that these problems are from having the SNAPSHOT repos
> (regular maven repo and plugin repo) in the maven repo stack?  I am
> basically in the habit of disabling the SNAPSHOT repos in any project I
> build because it does stuff like this.  And yes I always disable the
> SNAPSHOT repo in ApacheDS pom as well  :-)
>
> Its always been in the back of my mind to ask why it is enabled, but I
> figured that it allowed someone to build part of the SVN project without
> building the entire thing or something along those lines.
>
> Chris
>
> On 5/21/07, Alex Karasulu <akarasulu-1oDqGaOF3Lkdnm+yROfE0A@public.gmane.o
rg> wrote: 
>[/vbcol]


-- 
Regards,
Cordialement,
Emmanuel Lécharny
www.iktek.com

[ Post a follow-up to this message ]

I think this is already done, and if not, then this should be done.

On 5/21/07, Alex Karasulu <akarasulu-1oDqGaOF3Lkdnm+yROfE0A@public.gmane.org> wrote:
>
> I think this was due not to the SNAPSHOT repos but to the fact that we do
> not use
> a specific revision for all the plugins involved.
>
> If we disable the SNAPSHOT repos there will be other negative effects.
> For example
> when we are on a SNAPSHOT like say 1.5.1-SNAPSHOT then the snapshot jars
> are
> deployed to the apache snapshot repo.  If a user checks out the apacheds
> trunk and
> tries to build that instead of building the svn area with the dependent
> projects then
> those snapshots from shared and daemon will not be resolved.  Even worse
> if a user
> checks out apacheds/trunk/server-installers and tries to build that then
> it will fail if
> the SNAPSHOT repos are not visible.
>
> I think we just have to make sure we assign a specific revision to all the
> plugins we
> use instead of not including a revision for a plugin.  This will prevent
> the use of
> SNAPSHOT plugins I hope.
>
> There is also a pluginManagement section in the pom that we need to
> populate so
> we lock all plugins to a specific revision instead of allowing the use of
> SNAPSHOTs.
>
> Alex
>
> On 5/21/07, Chris Custine < chris.custine-Re5JQEeQqe8AvxtiuMwx3w@public.gm
ane.org> wrote: 
>


-- 
Regards,
Cordialement,
Emmanuel Lécharny
www.iktek.com

[ Post a follow-up to this message ]

Yeah we're not there 100% yet.  Yet another thing to do.  I will file a JIRA
on
doign this so we finally get to it.

Alex

On 5/21/07, Emmanuel Lecharny <elecharny-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote:[vbc
ol=seagreen]
>
> I think this is already done, and if not, then this should be done.
>
> On 5/21/07, Alex Karasulu <akarasulu-1oDqGaOF3Lkdnm+yROfE0A@public.gmane.o
rg > wrote: 
>
>
> --
> Regards,
> Cordialement,
> Emmanuel Lécharny
> www.iktek.com
>[/vbcol]

[ Post a follow-up to this message ]