A few things about the lift installer
2 views
Skip to first unread message
Marius
May 13, 2009, 2:41:31 AM5/13/09
to Lift
Hi,
I had it everything working having the git sources and built lift from
there. But then I tried the lift-installer. After I un-installed it
the M2_HOME env variable was not set back to the previous value.
Br's,
Marius
I had it everything working having the git sources and built lift from
there. But then I tried the lift-installer. After I un-installed it
the M2_HOME env variable was not set back to the previous value.
Br's,
Marius
Timothy Perrett
May 13, 2009, 3:34:01 AM5/13/09
to Lift Google Group
Which platform? windows? mac?
Sent from my iPhone
Sent from my iPhone
marius d.
May 13, 2009, 3:49:07 AM5/13/09
to Lift
Windows...
On May 13, 10:34 am, Timothy Perrett <timo...@getintheloop.eu> wrote:
> Which platform? windows? mac?
>
> Sent from my iPhone
>
On May 13, 10:34 am, Timothy Perrett <timo...@getintheloop.eu> wrote:
> Which platform? windows? mac?
>
> Sent from my iPhone
>
marius d.
May 13, 2009, 4:02:51 AM5/13/09
to Lift
One other thing ... I just installed on Windows using the installer
and I did not want it's maven and Java rebel.
After installation I noticed that in my M2_REPO the lift's artifacts
are not in my repository. Maybe I just don't understand how the
installer works.
Br's,
Marius
and I did not want it's maven and Java rebel.
After installation I noticed that in my M2_REPO the lift's artifacts
are not in my repository. Maybe I just don't understand how the
installer works.
Br's,
Marius
Timothy Perrett
May 13, 2009, 4:04:57 AM5/13/09
to Lift Google Group
Hmm I'll have to think about it - uninstalling PATH adjustment might
be quite difficult. Could probally remove the M2_HOME...
I'll have a think :-) any other feedback?
Sent from my iPhone
be quite difficult. Could probally remove the M2_HOME...
I'll have a think :-) any other feedback?
Sent from my iPhone
marius d.
May 13, 2009, 4:07:03 AM5/13/09
to Lift
Please see my previous post :)
On May 13, 11:04 am, Timothy Perrett <timo...@getintheloop.eu> wrote:
> Hmm I'll have to think about it - uninstalling PATH adjustment might
> be quite difficult. Could probally remove the M2_HOME...
>
> I'll have a think :-) any other feedback?
>
> Sent from my iPhone
>
On May 13, 11:04 am, Timothy Perrett <timo...@getintheloop.eu> wrote:
> Hmm I'll have to think about it - uninstalling PATH adjustment might
> be quite difficult. Could probally remove the M2_HOME...
>
> I'll have a think :-) any other feedback?
>
> Sent from my iPhone
>
Timothy Perrett
May 13, 2009, 4:09:52 AM5/13/09
to Lift Google Group
Ah right yes - it just does not do that :-)
The installer configures the environent ready for dev. We took the
descion some time ago to not try and replicate the maven functionality
as it will download all the release or snapshot jars for you.
Can we add some text that makes this clear?
Cheers, Tim
Sent from my iPhone
The installer configures the environent ready for dev. We took the
descion some time ago to not try and replicate the maven functionality
as it will download all the release or snapshot jars for you.
Can we add some text that makes this clear?
Cheers, Tim
Sent from my iPhone
marius d.
May 13, 2009, 4:23:36 AM5/13/09
to Lift
So ... I'm lost :) ... Where are the lift's binaries?
What I expected is this:
1. Install Lift via installer.
2. Create a lift project with Lift's archetypes
3. Build the project and run it
So the only thing that differs from what I normally do is step #1
where I'm not getting Lift's sources from GIT and I'm not building
Lift. I just wanted Lift's binaries and dependencies to be in my maven
repository.
I guess my expectation is wrong :( ... so how does the Lift installer
help someone that is new to Lift and just wants to try it out?
Please forgive me if I may seam blunt, it is not my intention, just
want to understand it ...
Br's,
Marius
On May 13, 11:09 am, Timothy Perrett <timo...@getintheloop.eu> wrote:
> Ah right yes - it just does not do that :-)
>
> The installer configures the environent ready for dev. We took the
> descion some time ago to not try and replicate the maven functionality
> as it will download all the release or snapshot jars for you.
>
> Can we add some text that makes this clear?
>
> Cheers, Tim
>
> Sent from my iPhone
>
What I expected is this:
1. Install Lift via installer.
2. Create a lift project with Lift's archetypes
3. Build the project and run it
So the only thing that differs from what I normally do is step #1
where I'm not getting Lift's sources from GIT and I'm not building
Lift. I just wanted Lift's binaries and dependencies to be in my maven
repository.
I guess my expectation is wrong :( ... so how does the Lift installer
help someone that is new to Lift and just wants to try it out?
Please forgive me if I may seam blunt, it is not my intention, just
want to understand it ...
Br's,
Marius
On May 13, 11:09 am, Timothy Perrett <timo...@getintheloop.eu> wrote:
> Ah right yes - it just does not do that :-)
>
> The installer configures the environent ready for dev. We took the
> descion some time ago to not try and replicate the maven functionality
> as it will download all the release or snapshot jars for you.
>
> Can we add some text that makes this clear?
>
> Cheers, Tim
>
> Sent from my iPhone
>
Timothy Perrett
May 13, 2009, 4:46:04 AM5/13/09
to lif...@googlegroups.com
The binaries are in our main maven repo of course on scala-tools... If we
put them in the installer, this does 2 things:
1. makes more work for us to regularly update the installers with the latest
JAR's and deploy to liftweb.net
2. Only saves the user about 1 min of download time during their first run.
The point of the installer is to get a users environment setup - from there
its just a simple case of running:
mvn archetype:generate -DarchetypeCatalog=http://scala-tools.org/
Job Done. Also, remember that we actually cannot distribute all the required
dependencies to make lift work because of licensing restrictions... So what
will it do when it needs those dependencies? Its going to fetch them from
the web. So, back to where we started... It might as well just download lift
too and get the latest version.
Thoughts?
Cheers, Tim
marius d.
May 13, 2009, 6:02:01 AM5/13/09
to Lift
Just thank you very very much ! :)
Br's,
Marius
On May 13, 11:46 am, Timothy Perrett <timo...@getintheloop.eu> wrote:
> The binaries are in our main maven repo of course on scala-tools... If we
> put them in the installer, this does 2 things:
>
> 1. makes more work for us to regularly update the installers with the latest
> JAR's and deploy to liftweb.net
>
> 2. Only saves the user about 1 min of download time during their first run.
>
> The point of the installer is to get a users environment setup - from there
> its just a simple case of running:
>
> mvn archetype:generate -DarchetypeCatalog=http://scala-tools.org/
>
> Job Done. Also, remember that we actually cannot distribute all the required
> dependencies to make lift work because of licensing restrictions... So what
> will it do when it needs those dependencies? Its going to fetch them from
> the web. So, back to where we started... It might as well just download lift
> too and get the latest version.
>
> Thoughts?
>
> Cheers, Tim
>
Br's,
Marius
On May 13, 11:46 am, Timothy Perrett <timo...@getintheloop.eu> wrote:
> The binaries are in our main maven repo of course on scala-tools... If we
> put them in the installer, this does 2 things:
>
> 1. makes more work for us to regularly update the installers with the latest
> JAR's and deploy to liftweb.net
>
> 2. Only saves the user about 1 min of download time during their first run.
>
> The point of the installer is to get a users environment setup - from there
> its just a simple case of running:
>
> mvn archetype:generate -DarchetypeCatalog=http://scala-tools.org/
>
> Job Done. Also, remember that we actually cannot distribute all the required
> dependencies to make lift work because of licensing restrictions... So what
> will it do when it needs those dependencies? Its going to fetch them from
> the web. So, back to where we started... It might as well just download lift
> too and get the latest version.
>
> Thoughts?
>
> Cheers, Tim
>
ph
Jun 15, 2009, 11:07:08 AM6/15/09
to Lift
Hello, I'm new to scala (and java) and I'm trying to start using lift.
I have scala installed (2.7.5) and I've ran lift installer and that
installed maven.
Now I'm trying to create a new project and this don't work:
[INFO] Scanning for projects...
[INFO] Searching repository for plugin with prefix: 'archetype'.
[INFO] Searching repository for plugin with prefix: 'http'.
[INFO]
------------------------------------------------------------------------
[ERROR] BUILD ERROR
[INFO]
------------------------------------------------------------------------
[INFO] The plugin 'org.apache.maven.plugins:maven-http-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 Jun 15 11:05:31 EDT 2009
[INFO] Final Memory: 2M/4M
[INFO]
------------------------------------------------------------------------
what am I missing?
On May 13, 4:46 am, Timothy Perrett <timo...@getintheloop.eu> wrote:
> The binaries are in our main maven repo of course on scala-tools... If we
> put them in the installer, this does 2 things:
>
> 1. makes more work for us to regularly update the installers with the latest
> JAR's and deploy to liftweb.net
>
> 2. Only saves the user about 1 min of download time during their first run.
>
> The point of the installer is to get a users environment setup - from there
> its just a simple case of running:
>
> mvn archetype:generate -DarchetypeCatalog=http://scala-tools.org/
>
> Job Done. Also, remember that we actually cannot distribute all the required
> dependencies to make lift work because of licensing restrictions... So what
> will it do when it needs those dependencies? Its going to fetch them from
> the web. So, back to where we started... It might as well just download lift
> too and get the latest version.
>
> Thoughts?
>
> Cheers, Tim
>
> > 3. Build theprojectand run it
I have scala installed (2.7.5) and I've ran lift installer and that
installed maven.
Now I'm trying to create a new project and this don't work:
[INFO] Scanning for projects...
[INFO] Searching repository for plugin with prefix: 'archetype'.
[INFO] Searching repository for plugin with prefix: 'http'.
[INFO]
------------------------------------------------------------------------
[ERROR] BUILD ERROR
[INFO]
------------------------------------------------------------------------
[INFO] The plugin 'org.apache.maven.plugins:maven-http-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 Jun 15 11:05:31 EDT 2009
[INFO] Final Memory: 2M/4M
[INFO]
------------------------------------------------------------------------
what am I missing?
On May 13, 4:46 am, Timothy Perrett <timo...@getintheloop.eu> wrote:
> The binaries are in our main maven repo of course on scala-tools... If we
> put them in the installer, this does 2 things:
>
> 1. makes more work for us to regularly update the installers with the latest
> JAR's and deploy to liftweb.net
>
> 2. Only saves the user about 1 min of download time during their first run.
>
> The point of the installer is to get a users environment setup - from there
> its just a simple case of running:
>
> mvn archetype:generate -DarchetypeCatalog=http://scala-tools.org/
>
> Job Done. Also, remember that we actually cannot distribute all the required
> dependencies to make lift work because of licensing restrictions... So what
> will it do when it needs those dependencies? Its going to fetch them from
> the web. So, back to where we started... It might as well just download lift
> too and get the latest version.
>
> Thoughts?
>
> Cheers, Tim
>
> On 13/05/2009 09:23, "marius d." <marius.dan...@gmail.com> wrote:
>
>
>
>
>
> > So ... I'm lost :) ... Where are the lift's binaries?
>
> > What I expected is this:
>
> > 1. Install Lift via installer.
> > 2. Create a liftprojectwith Lift's archetypes
>
>
>
>
>
> > So ... I'm lost :) ... Where are the lift's binaries?
>
> > What I expected is this:
>
> > 1. Install Lift via installer.
> > 3. Build theprojectand run it
>
> > So the only thing that differs from what I normally do is step #1
> > where I'm not getting Lift's sources from GIT and I'm not building
> > Lift. I just wanted Lift's binaries and dependencies to be in my maven
> > repository.
>
> > I guess my expectation is wrong :( ... so how does the Lift installer
> > help someone that is new to Lift and just wants to try it out?
>
> > Please forgive me if I may seam blunt, it is not my intention, just
> > want to understand it ...
>
> > Br's,
> > Marius
>
> > On May 13, 11:09 am, Timothy Perrett <timo...@getintheloop.eu> wrote:
> >> Ah right yes - it just does not do that :-)
>
> >> The installer configures the environent ready for dev. We took the
> >> descion some time ago to not try and replicate the maven functionality
> >> as it will download all the release or snapshot jars for you.
>
> >> Can we add some text that makes this clear?
>
> >> Cheers, Tim
>
> >> Sent from my iPhone
>
> >> On 13 May 2009, at 09:02, "marius d." <marius.dan...@gmail.com> wrote:
>
> >>> One other thing ... I just installed onWindowsusing the installer
> > So the only thing that differs from what I normally do is step #1
> > where I'm not getting Lift's sources from GIT and I'm not building
> > Lift. I just wanted Lift's binaries and dependencies to be in my maven
> > repository.
>
> > I guess my expectation is wrong :( ... so how does the Lift installer
> > help someone that is new to Lift and just wants to try it out?
>
> > Please forgive me if I may seam blunt, it is not my intention, just
> > want to understand it ...
>
> > Br's,
> > Marius
>
> > On May 13, 11:09 am, Timothy Perrett <timo...@getintheloop.eu> wrote:
> >> Ah right yes - it just does not do that :-)
>
> >> The installer configures the environent ready for dev. We took the
> >> descion some time ago to not try and replicate the maven functionality
> >> as it will download all the release or snapshot jars for you.
>
> >> Can we add some text that makes this clear?
>
> >> Cheers, Tim
>
> >> Sent from my iPhone
>
> >> On 13 May 2009, at 09:02, "marius d." <marius.dan...@gmail.com> wrote:
>
> >>> and I did not want it's maven and Java rebel.
>
> >>> After installation I noticed that in my M2_REPO the lift's artifacts
> >>> are not in my repository. Maybe I just don't understand how the
> >>> installer works.
>
> >>> Br's,
> >>> Marius
>
> >>> On May 13, 10:49 am, "marius d." <marius.dan...@gmail.com> wrote:
> >>>>Windows...
>
> >>>> On May 13, 10:34 am, Timothy Perrett <timo...@getintheloop.eu> wrote:
>
> >>>>> Which platform?windows? mac?
>
> >>> After installation I noticed that in my M2_REPO the lift's artifacts
> >>> are not in my repository. Maybe I just don't understand how the
> >>> installer works.
>
> >>> Br's,
> >>> Marius
>
> >>> On May 13, 10:49 am, "marius d." <marius.dan...@gmail.com> wrote:
> >>>>Windows...
>
> >>>> On May 13, 10:34 am, Timothy Perrett <timo...@getintheloop.eu> wrote:
>
ph
Jun 15, 2009, 11:26:05 AM6/15/09
to Lift
Hello, I new to scala/lift (and java). I'm trying to start using lift
and I've installed scala (2.7.5) and ran lift installer that installed
maven.
Now I'm trying to create a lift project and getting error:
On May 13, 4:46 am, Timothy Perrett <timo...@getintheloop.eu> wrote:
> The binaries are in our main maven repo of course on scala-tools... If we
> put them in the installer, this does 2 things:
>
> 1. makes more work for us to regularly update the installers with the latest
> JAR's and deploy to liftweb.net
>
> 2. Only saves the user about 1 min of download time during their first run.
>
> The point of the installer is to get a users environment setup - from there
> its just a simple case of running:
>
> mvn archetype:generate -DarchetypeCatalog=http://scala-tools.org/
>
> Job Done. Also, remember that we actually cannot distribute all the required
> dependencies to make lift work because of licensing restrictions... So what
> will it do when it needs those dependencies? Its going to fetch them from
> the web. So, back to where we started... It might as well just download lift
> too and get the latest version.
>
> Thoughts?
>
> Cheers, Tim
>
> >>> One other thing ... I just installed onWindowsusing the installer
and I've installed scala (2.7.5) and ran lift installer that installed
maven.
Now I'm trying to create a lift project and getting error:
[INFO] Scanning for projects...
[INFO] Searching repository for plugin with prefix: 'archetype'.
[INFO] Searching repository for plugin with prefix: 'http'.
[INFO]
------------------------------------------------------------------------
[ERROR] BUILD ERROR
[INFO]
------------------------------------------------------------------------
[INFO] The plugin 'org.apache.maven.plugins:maven-http-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 Jun 15 11:24:51 EDT 2009
[INFO] Searching repository for plugin with prefix: 'archetype'.
[INFO] Searching repository for plugin with prefix: 'http'.
[INFO]
------------------------------------------------------------------------
[ERROR] BUILD ERROR
[INFO]
------------------------------------------------------------------------
[INFO] The plugin 'org.apache.maven.plugins:maven-http-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] Final Memory: 2M/4M
[INFO]
------------------------------------------------------------------------
Is there anything I'm missing?
[INFO]
------------------------------------------------------------------------
On May 13, 4:46 am, Timothy Perrett <timo...@getintheloop.eu> wrote:
> The binaries are in our main maven repo of course on scala-tools... If we
> put them in the installer, this does 2 things:
>
> 1. makes more work for us to regularly update the installers with the latest
> JAR's and deploy to liftweb.net
>
> 2. Only saves the user about 1 min of download time during their first run.
>
> The point of the installer is to get a users environment setup - from there
> its just a simple case of running:
>
> mvn archetype:generate -DarchetypeCatalog=http://scala-tools.org/
>
> Job Done. Also, remember that we actually cannot distribute all the required
> dependencies to make lift work because of licensing restrictions... So what
> will it do when it needs those dependencies? Its going to fetch them from
> the web. So, back to where we started... It might as well just download lift
> too and get the latest version.
>
> Thoughts?
>
> Cheers, Tim
>
> >>> and I did not want it's maven and Java rebel.
>
> >>> After installation I noticed that in my M2_REPO the lift's artifacts
> >>> are not in my repository. Maybe I just don't understand how the
> >>> installer works.
>
> >>> Br's,
> >>> Marius
>
> >>> On May 13, 10:49 am, "marius d." <marius.dan...@gmail.com> wrote:
> >>>>Windows...
>
> >>>> On May 13, 10:34 am, Timothy Perrett <timo...@getintheloop.eu> wrote:
>
> >>>>> Which platform?windows? mac?
>
> >>> After installation I noticed that in my M2_REPO the lift's artifacts
> >>> are not in my repository. Maybe I just don't understand how the
> >>> installer works.
>
> >>> Br's,
> >>> Marius
>
> >>> On May 13, 10:49 am, "marius d." <marius.dan...@gmail.com> wrote:
> >>>>Windows...
>
> >>>> On May 13, 10:34 am, Timothy Perrett <timo...@getintheloop.eu> wrote:
>
ph
Jun 15, 2009, 11:27:14 AM6/15/09
to Lift
and here is the trace:
+ Error stacktraces are turned on.
org.apache.maven.lifecycle.LifecycleExecutionException: The plugin
(DefaultLifecycleExecutor.java:1303)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.getMojoDescriptor
(DefaultLifecycleExecutor.java:1542)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.segmentTaskListByAggregationNeeds
(DefaultLifecycleExecutor.java:405)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute
(DefaultLifecycleExecutor.java:137)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:336)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:129)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:287)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke
(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke
(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:
315)
at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:
430)
at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
Caused by:
org.apache.maven.plugin.version.PluginVersionNotFoundException: The
org.apache.maven.plugin.version.DefaultPluginVersionManager.resolvePluginVersion
(DefaultPluginVersionManager.java:229)
at
org.apache.maven.plugin.version.DefaultPluginVersionManager.resolvePluginVersion
(DefaultPluginVersionManager.java:91)
at org.apache.maven.plugin.DefaultPluginManager.verifyPlugin
(DefaultPluginManager.java:171)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.verifyPlugin
(DefaultLifecycleExecutor.java:1274)
... 14 more
+ Error stacktraces are turned on.
[INFO] Scanning for projects...
[INFO] Searching repository for plugin with prefix: 'archetype'.
[INFO] Searching repository for plugin with prefix: 'http'.
[INFO]
------------------------------------------------------------------------
[ERROR] BUILD ERROR
[INFO]
------------------------------------------------------------------------
[INFO] The plugin 'org.apache.maven.plugins:maven-http-plugin' does
not exist or no valid version could be found
[INFO]
------------------------------------------------------------------------
[INFO] Trace
[INFO] Searching repository for plugin with prefix: 'archetype'.
[INFO] Searching repository for plugin with prefix: 'http'.
[INFO]
------------------------------------------------------------------------
[ERROR] BUILD ERROR
[INFO]
------------------------------------------------------------------------
[INFO] The plugin 'org.apache.maven.plugins:maven-http-plugin' does
not exist or no valid version could be found
[INFO]
------------------------------------------------------------------------
org.apache.maven.lifecycle.LifecycleExecutionException: The plugin
'org.apache.maven.plugins:maven-http-plugin' does not exist or no
valid version could be found
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.verifyPlugin
valid version could be found
(DefaultLifecycleExecutor.java:1303)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.getMojoDescriptor
(DefaultLifecycleExecutor.java:1542)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.segmentTaskListByAggregationNeeds
(DefaultLifecycleExecutor.java:405)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute
(DefaultLifecycleExecutor.java:137)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:336)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:129)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:287)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke
(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke
(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:
315)
at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:
430)
at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
Caused by:
org.apache.maven.plugin.version.PluginVersionNotFoundException: The
plugin 'org.apache.maven.plugins:maven-http-plugin' does not exist or
no valid version could be found
at
no valid version could be found
org.apache.maven.plugin.version.DefaultPluginVersionManager.resolvePluginVersion
(DefaultPluginVersionManager.java:229)
at
org.apache.maven.plugin.version.DefaultPluginVersionManager.resolvePluginVersion
(DefaultPluginVersionManager.java:91)
at org.apache.maven.plugin.DefaultPluginManager.verifyPlugin
(DefaultPluginManager.java:171)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.verifyPlugin
(DefaultLifecycleExecutor.java:1274)
... 14 more
[INFO]
------------------------------------------------------------------------
[INFO] Total time: < 1 second
[INFO] Finished at: Mon Jun 15 11:26:04 EDT 2009
------------------------------------------------------------------------
[INFO] Total time: < 1 second
[INFO] Final Memory: 2M/4M
[INFO]
------------------------------------------------------------------------
[INFO]
------------------------------------------------------------------------
Reply all
Reply to author
Forward
0 new messages