[appengine-java] Re: Google Plugin for Eclipse 1.3 plans

[Philip]

This sounds like a good plan and I look forward to testing the new
plug-in.

- Philip


On Feb 4, 2:52 pm, Keith Platfoot  wrote:
> Hey all,
>
> Many of you have reported incompatibilities between the Google Plugin for
> Eclipse and other build systems/project structures, most notably Maven and
> J2EE/Dynamic Web Projects.  For example, issue 1515 (Eclipse plugin requires
> fixed location for war
> directory)
> has
> collected well over 100 stars, and a similar one in the GWT issue tracker
> has attracted a lot of attention as well.  Based on this feedback, we've
> decided to try and address as many of the incompatibilities as possible with
> our upcoming 1.3 release of the plugin.  To deliver on that goal, we want to
> share with your our current plans, and also let you know about a preview
> build that we'll make available so you can test the changes for yourself and
> give us feedback before final release.
>
> Our plans for the 1.3 release include 4 changes designed to make integration
> with Maven and J2EE projects easier:
>
>    1. The WAR directory can now be configured to be *any* project-relative
>    path (e.g. src/main/webapp if you're using Maven).  You'll also be able
>    to specify whether that directory is source-only (typical Maven/J2EE
>    scenario), or whether it should also function as the WAR output directory
>    from which to run/debug or deploy to App Engine.  If your WAR directory is
>    input *and* output (which will remain the default for new Web App
>    projects), the plugin will manage synchronizing the contents of WEB-INF/lib
>    WEB-INF/classes with your project's build path and compiled output.
>     Otherwise, we'll leave your WAR source directory alone and you'll need to
>    specify your WAR output location when launching, deploying, etc (the plugin
>    will remember the location once you set it the first time).
>    2. The Web App launch configuration UI is being redesigned to allow you
>    to see, and if necessary change, *any* of the launch arguments.
>     Previously, we were waiting until launch time to set many of these
>    arguments based on heuristics that were invisible and inaccessible to you.
>     Now you'll be in full control of how your projects get launched.  Also,
>    we're adding the capability to automatically migrate your launch
>    configurations when necessary, for example, updating the -javaagent flag
>    when changing App Engine SDKs.
>    3. GWT/App Engine projects will no longer require our SDK library on the
>    classpath.  This means Maven users will be able to pull in JAR files from
>    their M2 repository as they're accustomed to and the plugin won't mind a
>    bit.
>    4. The severity of any problem marker generated by the plugin will be
>    fully customizable via an Errors/Warnings preference page (similar to the
>    Java Errors/Warnings page), letting you specify either Error, Warning, or
>    Ignore.
>
> We'll also be including a few smaller features and bug fixes as well.
>
> What does everyone think about the 4 changes outlined above?  We've been
> testing the plugin against various Maven and J2EE configurations to try to
> ensure that we've eliminated the most critical roadblocks.  However, we're
> very interested in also having you folks take it for a spin before the
> official release date (slated for next month).  We're not quite ready yet,
> but stay tuned for a 1.3 preview build to be made available hopefully in a
> few weeks.  We'll distribute it as a zip file for dropin
> installation
> so
> it will come with the standard warnings and caveats (use with a clean
> Eclipse install and workspace, use at your risk, etc.).  However, it will
> hopefully give you a chance to give us any last-minute feedback about our
> changes before the final release.
>
> Thanks,
>
> Keith

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine for Java" group.
To post to this group, send email to google-appengine-j...@googlegroups.com.
To unsubscribe from this group, send email to 
google-appengine-java+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/google-appengine-java?hl=en.

[appengine-java] Re: Google Plugin for Eclipse 1.3 plans

[Philippe Marschall]

On Feb 4, 8:52 pm, Keith Platfoot  wrote:
> Hey all,
>
> Many of you have reported incompatibilities between the Google Plugin for
> Eclipse and other build systems/project structures, most notably Maven and
> J2EE/Dynamic Web Projects.  For example, issue 1515 (Eclipse plugin requires
> fixed location for war
> directory)
> has
> collected well over 100 stars, and a similar one in the GWT issue tracker
> has attracted a lot of attention as well.  Based on this feedback, we've
> decided to try and address as many of the incompatibilities as possible with
> our upcoming 1.3 release of the plugin.  To deliver on that goal, we want to
> share with your our current plans, and also let you know about a preview
> build that we'll make available so you can test the changes for yourself and
> give us feedback before final release.
>
> Our plans for the 1.3 release include 4 changes designed to make integration
> with Maven and J2EE projects easier:
>
>    1. The WAR directory can now be configured to be *any* project-relative
>    path (e.g. src/main/webapp if you're using Maven).  You'll also be able
>    to specify whether that directory is source-only (typical Maven/J2EE
>    scenario), or whether it should also function as the WAR output directory
>    from which to run/debug or deploy to App Engine.  If your WAR directory is
>    input *and* output (which will remain the default for new Web App
>    projects), the plugin will manage synchronizing the contents of WEB-INF/lib
>    WEB-INF/classes with your project's build path and compiled output.
>     Otherwise, we'll leave your WAR source directory alone and you'll need to
>    specify your WAR output location when launching, deploying, etc (the plugin
>    will remember the location once you set it the first time).
>    2. The Web App launch configuration UI is being redesigned to allow you
>    to see, and if necessary change, *any* of the launch arguments.
>     Previously, we were waiting until launch time to set many of these
>    arguments based on heuristics that were invisible and inaccessible to you.
>     Now you'll be in full control of how your projects get launched.  Also,
>    we're adding the capability to automatically migrate your launch
>    configurations when necessary, for example, updating the -javaagent flag
>    when changing App Engine SDKs.
>    3. GWT/App Engine projects will no longer require our SDK library on the
>    classpath.  This means Maven users will be able to pull in JAR files from
>    their M2 repository as they're accustomed to and the plugin won't mind a
>    bit.
>    4. The severity of any problem marker generated by the plugin will be
>    fully customizable via an Errors/Warnings preference page (similar to the
>    Java Errors/Warnings page), letting you specify either Error, Warning, or
>    Ignore.
>
> We'll also be including a few smaller features and bug fixes as well.
>
> What does everyone think about the 4 changes outlined above?  We've been
> testing the plugin against various Maven and J2EE configurations to try to
> ensure that we've eliminated the most critical roadblocks.  However, we're
> very interested in also having you folks take it for a spin before the
> official release date (slated for next month).  We're not quite ready yet,
> but stay tuned for a 1.3 preview build to be made available hopefully in a
> few weeks.  We'll distribute it as a zip file for dropin
> installation
> so
> it will come with the standard warnings and caveats (use with a clean
> Eclipse install and workspace, use at your risk, etc.).  However, it will
> hopefully give you a chance to give us any last-minute feedback about our
> changes before the final release.

Sounds like a good start. Ideally the maven eclipse plugin [1] could
be configured to automatically generate the configuration for the
Google Plugin and M2Eclipse [2] picking that up as well. Also an
archetype would help quick starting. I assume you're aware that you
get the most benefit out of that only when there are up to date Maven
artifacts wit good metadata in a publicly available repo, preferably
Maven central.

 [1] http://maven.apache.org/eclipse-plugin.html
 [2] http://m2eclipse.sonatype.org/

Cheers
Philippe

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine for Java" group.
To post to this group, send email to google-appengine-j...@googlegroups.com.
To unsubscribe from this group, send email to 
google-appengine-java+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/google-appengine-java?hl=en.

[appengine-java] Re: Google Plugin for Eclipse 1.3 plans

[Jake]

I'm hoping for a good way to resolve workspace dependencies in
Eclipse.  The m2eclipse plugin does this well, but that doesn't play
nicely with the maven-war-plugin, so it doesn't work for GAE.  Running
a Maven Install on each workspace dependency before deploying,
however, is still nicer than having to manually generate/copy jar
files.  I'm pretty new to Eclipse/Maven/GAE, so I don't know if it's
possible, but I'm hopeful! :)

Jake

On Feb 6, 12:40 pm, 杨浩  wrote:
> Where's the lastest plugin update sites for GAE Plugin?
> I will to test it!
>
> 2010/2/6 Philippe Marschall 
>
> > Sounds like a good start. Ideally the maven eclipse plugin [1] could
> > be configured to automatically generate the configuration for the
> > Google Plugin and M2Eclipse [2] picking that up as well. Also an
> > archetype would help quick starting. I assume you're aware that you
> > get the most benefit out of that only when there are up to date Maven
> > artifacts wit good metadata in a publicly available repo, preferably
> > Maven central.
>
> >  [1]http://maven.apache.org/eclipse-plugin.html
> >  [2]http://m2eclipse.sonatype.org/
>
> > Cheers
> > Philippe

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine for Java" group.
To post to this group, send email to google-appengine-j...@googlegroups.com.
To unsubscribe from this group, send email to 
google-appengine-java+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/google-appengine-java?hl=en.

[appengine-java] Re: Google Plugin for Eclipse 1.3 plans

[ga...@dynafocus.com]

This all sounds good.  However please make sure that it plays well
with other languages, especially scala.  I opened this ticket 3 months
ago with the scala eclipse plugin team.

https://lampsvn.epfl.ch/trac/scala/ticket/2614

Thanks


On Feb 4, 2:52 pm, Keith Platfoot  wrote:
> Hey all,
>
> Many of you have reported incompatibilities between the Google Plugin for
> Eclipse and other build systems/project structures, most notably Maven and
> J2EE/Dynamic Web Projects.  For example, issue 1515 (Eclipse plugin requires
> fixed location for war
> directory)
> has
> collected well over 100 stars, and a similar one in the GWT issue tracker
> has attracted a lot of attention as well.  Based on this feedback, we've
> decided to try and address as many of the incompatibilities as possible with
> our upcoming 1.3 release of the plugin.  To deliver on that goal, we want to
> share with your our current plans, and also let you know about a preview
> build that we'll make available so you can test the changes for yourself and
> give us feedback before final release.
>
> Our plans for the 1.3 release include 4 changes designed to make integration
> with Maven and J2EE projects easier:
>
>    1. The WAR directory can now be configured to be *any* project-relative
>    path (e.g. src/main/webapp if you're using Maven).  You'll also be able
>    to specify whether that directory is source-only (typical Maven/J2EE
>    scenario), or whether it should also function as the WAR output directory
>    from which to run/debug or deploy to App Engine.  If your WAR directory is
>    input *and* output (which will remain the default for new Web App
>    projects), the plugin will manage synchronizing the contents of WEB-INF/lib
>    WEB-INF/classes with your project's build path and compiled output.
>     Otherwise, we'll leave your WAR source directory alone and you'll need to
>    specify your WAR output location when launching, deploying, etc (the plugin
>    will remember the location once you set it the first time).
>    2. The Web App launch configuration UI is being redesigned to allow you
>    to see, and if necessary change, *any* of the launch arguments.
>     Previously, we were waiting until launch time to set many of these
>    arguments based on heuristics that were invisible and inaccessible to you.
>     Now you'll be in full control of how your projects get launched.  Also,
>    we're adding the capability to automatically migrate your launch
>    configurations when necessary, for example, updating the -javaagent flag
>    when changing App Engine SDKs.
>    3. GWT/App Engine projects will no longer require our SDK library on the
>    classpath.  This means Maven users will be able to pull in JAR files from
>    their M2 repository as they're accustomed to and the plugin won't mind a
>    bit.
>    4. The severity of any problem marker generated by the plugin will be
>    fully customizable via an Errors/Warnings preference page (similar to the
>    Java Errors/Warnings page), letting you specify either Error, Warning, or
>    Ignore.
>
> We'll also be including a few smaller features and bug fixes as well.
>
> What does everyone think about the 4 changes outlined above?  We've been
> testing the plugin against various Maven and J2EE configurations to try to
> ensure that we've eliminated the most critical roadblocks.  However, we're
> very interested in also having you folks take it for a spin before the
> official release date (slated for next month).  We're not quite ready yet,
> but stay tuned for a 1.3 preview build to be made available hopefully in a
> few weeks.  We'll distribute it as a zip file for dropin
> installation
> so
> it will come with the standard warnings and caveats (use with a clean
> Eclipse install and workspace, use at your risk, etc.).  However, it will
> hopefully give you a chance to give us any last-minute feedback about our
> changes before the final release.
>
> Thanks,
>
> Keith

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine for Java" group.
To post to this group, send email to google-appengine-j...@googlegroups.com.
To unsubscribe from this group, send email to 
google-appengine-java+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/google-appengine-java?hl=en.

[appengine-java] Re: Google Plugin for Eclipse 1.3 plans

[Marcel Overdijk]

SDK 1.3.1 was released today, so I was wondering if the 1.3 plugin is
also released, and more importantly if it contains better support for
maven as described in Keith's post.

On Feb 9, 10:11 pm, Hannu Leinonen  wrote:
> Allright,
>
> As I've stated before on the list, Maven + GAE Eclipse plugin
> integration is already possible! Exact instructions can be found in my
> blog post 
> athttp://hamandeggs.wordpress.com/2010/01/26/how-to-gae-eclipse-maven/I
> also have made an archetype for such a project. I'm currently using
> pretty much the same configuration in one of my projects and it works
> quite well (only downside being that you're required to clean the
> project on every Eclipse startup).
>
> Just type:
> mvn org.apache.maven.plugins:maven-archetype-plugin:2.0-alpha-4:generate \
>   -DarchetypeGroupId=org.beardedgeeks \
>   -DarchetypeArtifactId=gae-eclipse-maven-archetype \
>   -DarchetypeVersion=1.1.1 \
>
> -DarchetypeRepository=http://beardedgeeks.googlecode.com/svn/repository/releases
>
> -Hannu
>
> On 8.2.2010 20:35, Jake wrote:
>
>
>
> > I'm hoping for a good way to resolve workspace dependencies in
> > Eclipse.  The m2eclipse plugin does this well, but that doesn't play
> > nicely with the maven-war-plugin, so it doesn't work for GAE.  Running
> > a Maven Install on each workspace dependency before deploying,
> > however, is still nicer than having to manually generate/copy jar
> > files.  I'm pretty new to Eclipse/Maven/GAE, so I don't know if it's
> > possible, but I'm hopeful! :)
>
> > Jake
>
> > On Feb 6, 12:40 pm, 杨浩  wrote:
> >> Where's the lastest plugin update sites for GAE Plugin?
> >> I will to test it!
>
> >> 2010/2/6 Philippe Marschall 
>
> >>> Sounds like a good start. Ideally the maven eclipse plugin [1] could
> >>> be configured to automatically generate the configuration for the
> >>> Google Plugin and M2Eclipse [2] picking that up as well. Also an
> >>> archetype would help quick starting. I assume you're aware that you
> >>> get the most benefit out of that only when there are up to date Maven
> >>> artifacts wit good metadata in a publicly available repo, preferably
> >>> Maven central.
>
> >>>  [1]http://maven.apache.org/eclipse-plugin.html
> >>>  [2]http://m2eclipse.sonatype.org/
>
> >>> Cheers
> >>> Philippe

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine for Java" group.
To post to this group, send email to google-appengine-j...@googlegroups.com.
To unsubscribe from this group, send email to 
google-appengine-java+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/google-appengine-java?hl=en.

[appengine-java] Re: Google Plugin for Eclipse 1.3 plans

[Sudhir]

Has anyone else noticed that installing GAE SDK 1.3.1 screws up the
Google Plugin? It keeps throwing class loader exceptions and renders
the run configs useless.

On Feb 11, 9:23 pm, Keith Platfoot  wrote:
> Hi Marcel,
>
> The Eclipse plugin has a different release cycle than the App Engine SDK, so
> no, the current plugin version remains 1.2.  Look the 1.3 version of the
> plugin to be released in March (with a preview build available near the end
> of this month).
>
> Keith
>
> On Thu, Feb 11, 2010 at 9:09 AM, Marcel Overdijk
> wrote:
>
>
>
> > SDK 1.3.1 was released today, so I was wondering if the 1.3 plugin is
> > also released, and more importantly if it contains better support for
> > maven as described in Keith's post.
>
> > On Feb 9, 10:11 pm, Hannu Leinonen  wrote:
> > > Allright,
>
> > > As I've stated before on the list, Maven + GAE Eclipse plugin
> > > integration is already possible! Exact instructions can be found in my
> > > blog post athttp://
> > hamandeggs.wordpress.com/2010/01/26/how-to-gae-eclipse-maven/I
> > > also have made an archetype for such a project. I'm currently using
> > > pretty much the same configuration in one of my projects and it works
> > > quite well (only downside being that you're required to clean the
> > > project on every Eclipse startup).
>
> > > Just type:
> > > mvn org.apache.maven.plugins:maven-archetype-plugin:2.0-alpha-4:generate
> > \
> > >   -DarchetypeGroupId=org.beardedgeeks \
> > >   -DarchetypeArtifactId=gae-eclipse-maven-archetype \
> > >   -DarchetypeVersion=1.1.1 \
>
> > > -DarchetypeRepository=
> >http://beardedgeeks.googlecode.com/svn/repository/releases
>
> > > -Hannu
>
> > > On 8.2.2010 20:35, Jake wrote:
>
> > > > I'm hoping for a good way to resolve workspace dependencies in
> > > > Eclipse.  The m2eclipse plugin does this well, but that doesn't play
> > > > nicely with the maven-war-plugin, so it doesn't work for GAE.  Running
> > > > a Maven Install on each workspace dependency before deploying,
> > > > however, is still nicer than having to manually generate/copy jar
> > > > files.  I'm pretty new to Eclipse/Maven/GAE, so I don't know if it's
> > > > possible, but I'm hopeful! :)
>
> > > > Jake
>
> > > > On Feb 6, 12:40 pm, 杨浩  wrote:
> > > >> Where's the lastest plugin update sites for GAE Plugin?
> > > >> I will to test it!
>
> > > >> 2010/2/6 Philippe Marschall 
>
> > > >>> Sounds like a good start. Ideally the maven eclipse plugin [1] could
> > > >>> be configured to automatically generate the configuration for the
> > > >>> Google Plugin and M2Eclipse [2] picking that up as well. Also an
> > > >>> archetype would help quick starting. I assume you're aware that you
> > > >>> get the most benefit out of that only when there are up to date Maven
> > > >>> artifacts wit good metadata in a publicly available repo, preferably
> > > >>> Maven central.
>
> > > >>>  [1]http://maven.apache.org/eclipse-plugin.html
> > > >>>  [2]http://m2eclipse.sonatype.org/
>
> > > >>> Cheers
> > > >>> Philippe
>
> > --
> > You received this message because you are subscribed to the Google Groups
> > "Google App Engine for Java" group.
> > To post to this group, send email to
> > google-appengine-j...@googlegroups.com.
> > To unsubscribe from this group, send email to
> > google-appengine-java+unsubscr...@googlegroups.com > unsubscr...@googlegroups.com>
> > .
> > For more options, visit this group at
> >http://groups.google.com/group/google-appengine-java?hl=en.

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine for Java" group.
To post to this group, send email to google-appengine-j...@googlegroups.com.
To unsubscribe from this group, send email to 
google-appengine-java+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/google-appengine-java?hl=en.

[appengine-java] Re: Google Plugin for Eclipse 1.3 plans

[Sudhir]

Yeah... I've raised an issue
http://code.google.com/p/googleappengine/issues/detail?id=2758&sort=-opened&colspec=ID%20Type%20Status%20Priority%20Stars%20Owner%20Summary%20Log%20Component%20Opened
with the stacktrace.

On Feb 11, 11:51 pm, Rajeev Dayal  wrote:
> Can you provide a stack trace?
>
>
>
> On Thu, Feb 11, 2010 at 1:29 PM, Sudhir  wrote:
> > Has anyone else noticed that installing GAE SDK 1.3.1 screws up the
> > Google Plugin? It keeps throwing class loader exceptions and renders
> > the run configs useless.
>
> > On Feb 11, 9:23 pm, Keith Platfoot  wrote:
> > > Hi Marcel,
>
> > > The Eclipse plugin has a different release cycle than the App Engine SDK,
> > so
> > > no, the current plugin version remains 1.2.  Look the 1.3 version of the
> > > plugin to be released in March (with a preview build available near the
> > end
> > > of this month).
>
> > > Keith
>
> > > On Thu, Feb 11, 2010 at 9:09 AM, Marcel Overdijk
> > > wrote:
>
> > > > SDK 1.3.1 was released today, so I was wondering if the 1.3 plugin is
> > > > also released, and more importantly if it contains better support for
> > > > maven as described in Keith's post.
>
> > > > On Feb 9, 10:11 pm, Hannu Leinonen  wrote:
> > > > > Allright,
>
> > > > > As I've stated before on the list, Maven + GAE Eclipse plugin
> > > > > integration is already possible! Exact instructions can be found in
> > my
> > > > > blog post athttp://
> > > > hamandeggs.wordpress.com/2010/01/26/how-to-gae-eclipse-maven/I
> > > > > also have made an archetype for such a project. I'm currently using
> > > > > pretty much the same configuration in one of my projects and it works
> > > > > quite well (only downside being that you're required to clean the
> > > > > project on every Eclipse startup).
>
> > > > > Just type:
> > > > > mvn
> > org.apache.maven.plugins:maven-archetype-plugin:2.0-alpha-4:generate
> > > > \
> > > > >   -DarchetypeGroupId=org.beardedgeeks \
> > > > >   -DarchetypeArtifactId=gae-eclipse-maven-archetype \
> > > > >   -DarchetypeVersion=1.1.1 \
>
> > > > > -DarchetypeRepository=
> > > >http://beardedgeeks.googlecode.com/svn/repository/releases
>
> > > > > -Hannu
>
> > > > > On 8.2.2010 20:35, Jake wrote:
>
> > > > > > I'm hoping for a good way to resolve workspace dependencies in
> > > > > > Eclipse.  The m2eclipse plugin does this well, but that doesn't
> > play
> > > > > > nicely with the maven-war-plugin, so it doesn't work for GAE.
> >  Running
> > > > > > a Maven Install on each workspace dependency before deploying,
> > > > > > however, is still nicer than having to manually generate/copy jar
> > > > > > files.  I'm pretty new to Eclipse/Maven/GAE, so I don't know if
> > it's
> > > > > > possible, but I'm hopeful! :)
>
> > > > > > Jake
>
> > > > > > On Feb 6, 12:40 pm, 杨浩  wrote:
> > > > > >> Where's the lastest plugin update sites for GAE Plugin?
> > > > > >> I will to test it!
>
> > > > > >> 2010/2/6 Philippe Marschall 
>
> > > > > >>> Sounds like a good start. Ideally the maven eclipse plugin [1]
> > could
> > > > > >>> be configured to automatically generate the configuration for the
> > > > > >>> Google Plugin and M2Eclipse [2] picking that up as well. Also an
> > > > > >>> archetype would help quick starting. I assume you're aware that
> > you
> > > > > >>> get the most benefit out of that only when there are up to date
> > Maven
> > > > > >>> artifacts wit good metadata in a publicly available repo,
> > preferably
> > > > > >>> Maven central.
>
> > > > > >>>  [1]http://maven.apache.org/eclipse-plugin.html
> > > > > >>>  [2]http://m2eclipse.sonatype.org/
>
> > > > > >>> Cheers
> > > > > >>> Philippe
>
> > > > --
> > > > You received this message because you are subscribed to the Google
> > Groups
> > > > "Google App Engine for Java" group.
> > > > To post to this group, send email to
> > > > google-appengine-j...@googlegroups.com.
> > > > To unsubscribe from this group, send email to
> > > > google-appengine-java+unsubscr...@googlegroups.com > > >  unsubscr...@googlegroups.com> > unsubscr...@googlegroups.com>
> > > > .
> > > > For more options, visit this group at
> > > >http://groups.google.com/group/google-appengine-java?hl=en.
>
> > --
> > You received this message because you are subscribed to the Google Groups
> > "Google App Engine for Java" group.
> > To post to this group, send email to
> > google-appengine-j...@googlegroups.com.
> > To unsubscribe from this group, send email to
> > google-appengine-java+unsubscr...@googlegroups.com > unsubscr...@googlegroups.com>
> > .
> > For more options, visit this group at
> >http://groups.google.com/group/google-appengine-java?hl=en.

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine for Java" group.
To post to this group, send email to google-appengine-j...@googlegroups.com.
To unsubscribe from this group, send email to 
google-appengine-java+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/go

[appengine-java] Re: Google Plugin for Eclipse 1.3 plans

[Matthew McGinty]

Keith,

Please address #2739 :

http://code.google.com/p/googleappengine/issues/detail?id=2739

at the same time you address #1515.
My project (Open BlueDragon) needs to be easily switched between non-
GAE and GAE environments.

Thanks.

Matt McGinty



On Feb 4, 2:52 pm, Keith Platfoot  wrote:
> Hey all,
>
> Many of you have reported incompatibilities between the Google Plugin for
> Eclipse and other build systems/project structures, most notably Maven and
> J2EE/Dynamic Web Projects.  For example, issue 1515 (Eclipse plugin requires
> fixed location for war
> directory)
> has
> collected well over 100 stars, and a similar one in the GWT issue tracker
> has attracted a lot of attention as well.  Based on this feedback, we've
> decided to try and address as many of the incompatibilities as possible with
> our upcoming 1.3 release of the plugin.  To deliver on that goal, we want to
> share with your our current plans, and also let you know about a preview
> build that we'll make available so you can test the changes for yourself and
> give us feedback before final release.
>
> Our plans for the 1.3 release include 4 changes designed to make integration
> with Maven and J2EE projects easier:
>
>    1. The WAR directory can now be configured to be *any* project-relative
>    path (e.g. src/main/webapp if you're using Maven).  You'll also be able
>    to specify whether that directory is source-only (typical Maven/J2EE
>    scenario), or whether it should also function as the WAR output directory
>    from which to run/debug or deploy to App Engine.  If your WAR directory is
>    input *and* output (which will remain the default for new Web App
>    projects), the plugin will manage synchronizing the contents of WEB-INF/lib
>    WEB-INF/classes with your project's build path and compiled output.
>     Otherwise, we'll leave your WAR source directory alone and you'll need to
>    specify your WAR output location when launching, deploying, etc (the plugin
>    will remember the location once you set it the first time).
>    2. The Web App launch configuration UI is being redesigned to allow you
>    to see, and if necessary change, *any* of the launch arguments.
>     Previously, we were waiting until launch time to set many of these
>    arguments based on heuristics that were invisible and inaccessible to you.
>     Now you'll be in full control of how your projects get launched.  Also,
>    we're adding the capability to automatically migrate your launch
>    configurations when necessary, for example, updating the -javaagent flag
>    when changing App Engine SDKs.
>    3. GWT/App Engine projects will no longer require our SDK library on the
>    classpath.  This means Maven users will be able to pull in JAR files from
>    their M2 repository as they're accustomed to and the plugin won't mind a
>    bit.
>    4. The severity of any problem marker generated by the plugin will be
>    fully customizable via an Errors/Warnings preference page (similar to the
>    Java Errors/Warnings page), letting you specify either Error, Warning, or
>    Ignore.
>
> We'll also be including a few smaller features and bug fixes as well.
>
> What does everyone think about the 4 changes outlined above?  We've been
> testing the plugin against various Maven and J2EE configurations to try to
> ensure that we've eliminated the most critical roadblocks.  However, we're
> very interested in also having you folks take it for a spin before the
> official release date (slated for next month).  We're not quite ready yet,
> but stay tuned for a 1.3 preview build to be made available hopefully in a
> few weeks.  We'll distribute it as a zip file for dropin
> installation
> so
> it will come with the standard warnings and caveats (use with a clean
> Eclipse install and workspace, use at your risk, etc.).  However, it will
> hopefully give you a chance to give us any last-minute feedback about our
> changes before the final release.
>
> Thanks,
>
> Keith

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine for Java" group.
To post to this group, send email to google-appengine-j...@googlegroups.com.
To unsubscribe from this group, send email to 
google-appengine-java+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/google-appengine-java?hl=en.

[appengine-java] Re: Google Plugin for Eclipse 1.3 plans

[KasperDK]

Hi all,

Where exactly is the Google Plugin for Eclipse preview located ? Or is
it not released yet ? Im dying to try it out :-)

Cheers,

:-) Kasper

On Feb 4, 8:52 pm, Keith Platfoot  wrote:
> Hey all,
>
> Many of you have reported incompatibilities between the Google Plugin for
> Eclipse and other build systems/project structures, most notably Maven and
> J2EE/Dynamic Web Projects.  For example, issue 1515 (Eclipse plugin requires
> fixed location for war
> directory)
> has
> collected well over 100 stars, and a similar one in the GWT issue tracker
> has attracted a lot of attention as well.  Based on this feedback, we've
> decided to try and address as many of the incompatibilities as possible with
> our upcoming 1.3 release of the plugin.  To deliver on that goal, we want to
> share with your our current plans, and also let you know about a preview
> build that we'll make available so you can test the changes for yourself and
> give us feedback before final release.
>
> Our plans for the 1.3 release include 4 changes designed to make integration
> with Maven and J2EE projects easier:
>
>    1. The WAR directory can now be configured to be *any* project-relative
>    path (e.g. src/main/webapp if you're using Maven).  You'll also be able
>    to specify whether that directory is source-only (typical Maven/J2EE
>    scenario), or whether it should also function as the WAR output directory
>    from which to run/debug or deploy to App Engine.  If your WAR directory is
>    input *and* output (which will remain the default for new Web App
>    projects), the plugin will manage synchronizing the contents of WEB-INF/lib
>    WEB-INF/classes with your project's build path and compiled output.
>     Otherwise, we'll leave your WAR source directory alone and you'll need to
>    specify your WAR output location when launching, deploying, etc (the plugin
>    will remember the location once you set it the first time).
>    2. The Web App launch configuration UI is being redesigned to allow you
>    to see, and if necessary change, *any* of the launch arguments.
>     Previously, we were waiting until launch time to set many of these
>    arguments based on heuristics that were invisible and inaccessible to you.
>     Now you'll be in full control of how your projects get launched.  Also,
>    we're adding the capability to automatically migrate your launch
>    configurations when necessary, for example, updating the -javaagent flag
>    when changing App Engine SDKs.
>    3. GWT/App Engine projects will no longer require our SDK library on the
>    classpath.  This means Maven users will be able to pull in JAR files from
>    their M2 repository as they're accustomed to and the plugin won't mind a
>    bit.
>    4. The severity of any problem marker generated by the plugin will be
>    fully customizable via an Errors/Warnings preference page (similar to the
>    Java Errors/Warnings page), letting you specify either Error, Warning, or
>    Ignore.
>
> We'll also be including a few smaller features and bug fixes as well.
>
> What does everyone think about the 4 changes outlined above?  We've been
> testing the plugin against various Maven and J2EE configurations to try to
> ensure that we've eliminated the most critical roadblocks.  However, we're
> very interested in also having you folks take it for a spin before the
> official release date (slated for next month).  We're not quite ready yet,
> but stay tuned for a 1.3 preview build to be made available hopefully in a
> few weeks.  We'll distribute it as a zip file for dropin
> installation
> so
> it will come with the standard warnings and caveats (use with a clean
> Eclipse install and workspace, use at your risk, etc.).  However, it will
> hopefully give you a chance to give us any last-minute feedback about our
> changes before the final release.
>
> Thanks,
>
> Keith

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine for Java" group.
To post to this group, send email to google-appengine-j...@googlegroups.com.
To unsubscribe from this group, send email to 
google-appengine-java+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/google-appengine-java?hl=en.

Re: [appengine-java] Re: Google Plugin for Eclipse 1.3 plans

[杨浩]

Where's the lastest plugin update sites for GAE Plugin?
I will to test it!

2010/2/6 Philippe Marschall 

> Sounds like a good start. Ideally the maven eclipse plugin [1] could
> be configured to automatically generate the configuration for the
> Google Plugin and M2Eclipse [2] picking that up as well. Also an
> archetype would help quick starting. I assume you're aware that you
> get the most benefit out of that only when there are up to date Maven
> artifacts wit good metadata in a publicly available repo, preferably
> Maven central.
>
>  [1] http://maven.apache.org/eclipse-plugin.html
>  [2] http://m2eclipse.sonatype.org/
>
> Cheers
> Philippe
>

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine for Java" group.
To post to this group, send email to google-appengine-j...@googlegroups.com.
To unsubscribe from this group, send email to 
google-appengine-java+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/google-appengine-java?hl=en.

Re: [appengine-java] Re: Google Plugin for Eclipse 1.3 plans

[Ikai L (Google)]

I'm a bit of a Scala enthusiast myself, so I'm glad to see folks using Scala
on App Engine. Last I checked, Miles was swamped, but here's hoping he can
do this!

On Tue, Feb 9, 2010 at 8:57 AM, ga...@dynafocus.com wrote:

> This all sounds good.  However please make sure that it plays well
> with other languages, especially scala.  I opened this ticket 3 months
> ago with the scala eclipse plugin team.
>
> https://lampsvn.epfl.ch/trac/scala/ticket/2614
>
> Thanks
>
>
> On Feb 4, 2:52 pm, Keith Platfoot  wrote:
> > Hey all,
> >
> > Many of you have reported incompatibilities between the Google Plugin for
> > Eclipse and other build systems/project structures, most notably Maven
> and
> > J2EE/Dynamic Web Projects.  For example, issue 1515 (Eclipse plugin
> requires
> > fixed location for war
> > directory)<
> http://code.google.com/p/googleappengine/issues/detail?id=1515>
> > has
> > collected well over 100 stars, and a similar one in the GWT issue tracker
> > has attracted a lot of attention as well.  Based on this feedback, we've
> > decided to try and address as many of the incompatibilities as possible
> with
> > our upcoming 1.3 release of the plugin.  To deliver on that goal, we want
> to
> > share with your our current plans, and also let you know about a preview
> > build that we'll make available so you can test the changes for yourself
> and
> > give us feedback before final release.
> >
> > Our plans for the 1.3 release include 4 changes designed to make
> integration
> > with Maven and J2EE projects easier:
> >
> >1. The WAR directory can now be configured to be *any*
> project-relative
> >path (e.g. src/main/webapp if you're using Maven).  You'll also be
> able
> >to specify whether that directory is source-only (typical Maven/J2EE
> >scenario), or whether it should also function as the WAR output
> directory
> >from which to run/debug or deploy to App Engine.  If your WAR
> directory is
> >input *and* output (which will remain the default for new Web App
> >projects), the plugin will manage synchronizing the contents of
> WEB-INF/lib
> >WEB-INF/classes with your project's build path and compiled output.
> > Otherwise, we'll leave your WAR source directory alone and you'll
> need to
> >specify your WAR output location when launching, deploying, etc (the
> plugin
> >will remember the location once you set it the first time).
> >2. The Web App launch configuration UI is being redesigned to allow
> you
> >to see, and if necessary change, *any* of the launch arguments.
> > Previously, we were waiting until launch time to set many of these
> >arguments based on heuristics that were invisible and inaccessible to
> you.
> > Now you'll be in full control of how your projects get launched.
>  Also,
> >we're adding the capability to automatically migrate your launch
> >configurations when necessary, for example, updating the -javaagent
> flag
> >when changing App Engine SDKs.
> >3. GWT/App Engine projects will no longer require our SDK library on
> the
> >classpath.  This means Maven users will be able to pull in JAR files
> from
> >their M2 repository as they're accustomed to and the plugin won't mind
> a
> >bit.
> >4. The severity of any problem marker generated by the plugin will be
> >fully customizable via an Errors/Warnings preference page (similar to
> the
> >Java Errors/Warnings page), letting you specify either Error, Warning,
> or
> >Ignore.
> >
> > We'll also be including a few smaller features and bug fixes as well.
> >
> > What does everyone think about the 4 changes outlined above?  We've been
> > testing the plugin against various Maven and J2EE configurations to try
> to
> > ensure that we've eliminated the most critical roadblocks.  However,
> we're
> > very interested in also having you folks take it for a spin before the
> > official release date (slated for next month).  We're not quite ready
> yet,
> > but stay tuned for a 1.3 preview build to be made available hopefully in
> a
> > few weeks.  We'll distribute it as a zip file for dropin
> > installation
> > so
> > it will come with the standard warnings and caveats (use with a clean
> > Eclipse install and workspace, use at your risk, etc.).  However, it will
> > hopefully give you a chance to give us any last-minute feedback about our
> > changes before the final release.
> >
> > Thanks,
> >
> > Keith
>
> --
> You received this message because you are subscribed to the Google Groups
> "Google App Engine for Java" group.
> To post to this group, send email to
> google-appengine-j...@googlegroups.com.
> To unsubscribe from this group, send email to
> google-appengine-java+unsubscr...@googlegroups.com
> .
> For more options, visit this group at
> http://groups.google.com/group/google-appengine-java?hl=en.
>
>


-- 
Ikai Lan
Developer Programs Engineer, Google App Engine

Re: [appengine-java] Re: Google Plugin for Eclipse 1.3 plans

[Miguel Méndez]

I filed http://code.google.com/p/google-web-toolkit/issues/detail?id=4608.
 GPE should NPE even if the source language is Scala.

On Tue, Feb 9, 2010 at 11:57 AM, ga...@dynafocus.com wrote:

> This all sounds good.  However please make sure that it plays well
> with other languages, especially scala.  I opened this ticket 3 months
> ago with the scala eclipse plugin team.
>
> https://lampsvn.epfl.ch/trac/scala/ticket/2614
>
> Thanks
>
>
> On Feb 4, 2:52 pm, Keith Platfoot  wrote:
> > Hey all,
> >
> > Many of you have reported incompatibilities between the Google Plugin for
> > Eclipse and other build systems/project structures, most notably Maven
> and
> > J2EE/Dynamic Web Projects.  For example, issue 1515 (Eclipse plugin
> requires
> > fixed location for war
> > directory)<
> http://code.google.com/p/googleappengine/issues/detail?id=1515>
> > has
> > collected well over 100 stars, and a similar one in the GWT issue tracker
> > has attracted a lot of attention as well.  Based on this feedback, we've
> > decided to try and address as many of the incompatibilities as possible
> with
> > our upcoming 1.3 release of the plugin.  To deliver on that goal, we want
> to
> > share with your our current plans, and also let you know about a preview
> > build that we'll make available so you can test the changes for yourself
> and
> > give us feedback before final release.
> >
> > Our plans for the 1.3 release include 4 changes designed to make
> integration
> > with Maven and J2EE projects easier:
> >
> >1. The WAR directory can now be configured to be *any*
> project-relative
> >path (e.g. src/main/webapp if you're using Maven).  You'll also be
> able
> >to specify whether that directory is source-only (typical Maven/J2EE
> >scenario), or whether it should also function as the WAR output
> directory
> >from which to run/debug or deploy to App Engine.  If your WAR
> directory is
> >input *and* output (which will remain the default for new Web App
> >projects), the plugin will manage synchronizing the contents of
> WEB-INF/lib
> >WEB-INF/classes with your project's build path and compiled output.
> > Otherwise, we'll leave your WAR source directory alone and you'll
> need to
> >specify your WAR output location when launching, deploying, etc (the
> plugin
> >will remember the location once you set it the first time).
> >2. The Web App launch configuration UI is being redesigned to allow
> you
> >to see, and if necessary change, *any* of the launch arguments.
> > Previously, we were waiting until launch time to set many of these
> >arguments based on heuristics that were invisible and inaccessible to
> you.
> > Now you'll be in full control of how your projects get launched.
>  Also,
> >we're adding the capability to automatically migrate your launch
> >configurations when necessary, for example, updating the -javaagent
> flag
> >when changing App Engine SDKs.
> >3. GWT/App Engine projects will no longer require our SDK library on
> the
> >classpath.  This means Maven users will be able to pull in JAR files
> from
> >their M2 repository as they're accustomed to and the plugin won't mind
> a
> >bit.
> >4. The severity of any problem marker generated by the plugin will be
> >fully customizable via an Errors/Warnings preference page (similar to
> the
> >Java Errors/Warnings page), letting you specify either Error, Warning,
> or
> >Ignore.
> >
> > We'll also be including a few smaller features and bug fixes as well.
> >
> > What does everyone think about the 4 changes outlined above?  We've been
> > testing the plugin against various Maven and J2EE configurations to try
> to
> > ensure that we've eliminated the most critical roadblocks.  However,
> we're
> > very interested in also having you folks take it for a spin before the
> > official release date (slated for next month).  We're not quite ready
> yet,
> > but stay tuned for a 1.3 preview build to be made available hopefully in
> a
> > few weeks.  We'll distribute it as a zip file for dropin
> > installation
> > so
> > it will come with the standard warnings and caveats (use with a clean
> > Eclipse install and workspace, use at your risk, etc.).  However, it will
> > hopefully give you a chance to give us any last-minute feedback about our
> > changes before the final release.
> >
> > Thanks,
> >
> > Keith
>
> --
> You received this message because you are subscribed to the Google Groups
> "Google App Engine for Java" group.
> To post to this group, send email to
> google-appengine-j...@googlegroups.com.
> To unsubscribe from this group, send email to
> google-appengine-java+unsubscr...@googlegroups.com
> .
> For more options, visit this group at
> http://groups.google.com/group/google-appengine-java?hl=en.
>
>


-- 
Miguel

-- 
You received this message because you are subscribed to the Google Groups 

Re: [appengine-java] Re: Google Plugin for Eclipse 1.3 plans

[Hannu Leinonen]

Allright,

As I've stated before on the list, Maven + GAE Eclipse plugin
integration is already possible! Exact instructions can be found in my
blog post at
http://hamandeggs.wordpress.com/2010/01/26/how-to-gae-eclipse-maven/ I
also have made an archetype for such a project. I'm currently using
pretty much the same configuration in one of my projects and it works
quite well (only downside being that you're required to clean the
project on every Eclipse startup).

Just type:
mvn org.apache.maven.plugins:maven-archetype-plugin:2.0-alpha-4:generate \
  -DarchetypeGroupId=org.beardedgeeks \
  -DarchetypeArtifactId=gae-eclipse-maven-archetype \
  -DarchetypeVersion=1.1.1 \

-DarchetypeRepository=http://beardedgeeks.googlecode.com/svn/repository/releases


-Hannu

On 8.2.2010 20:35, Jake wrote:
> I'm hoping for a good way to resolve workspace dependencies in
> Eclipse.  The m2eclipse plugin does this well, but that doesn't play
> nicely with the maven-war-plugin, so it doesn't work for GAE.  Running
> a Maven Install on each workspace dependency before deploying,
> however, is still nicer than having to manually generate/copy jar
> files.  I'm pretty new to Eclipse/Maven/GAE, so I don't know if it's
> possible, but I'm hopeful! :)
> 
> Jake
> 
> On Feb 6, 12:40 pm, 杨浩  wrote:
>> Where's the lastest plugin update sites for GAE Plugin?
>> I will to test it!
>>
>> 2010/2/6 Philippe Marschall 
>>
>>> Sounds like a good start. Ideally the maven eclipse plugin [1] could
>>> be configured to automatically generate the configuration for the
>>> Google Plugin and M2Eclipse [2] picking that up as well. Also an
>>> archetype would help quick starting. I assume you're aware that you
>>> get the most benefit out of that only when there are up to date Maven
>>> artifacts wit good metadata in a publicly available repo, preferably
>>> Maven central.
>>
>>>  [1]http://maven.apache.org/eclipse-plugin.html
>>>  [2]http://m2eclipse.sonatype.org/
>>
>>> Cheers
>>> Philippe
> 

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine for Java" group.
To post to this group, send email to google-appengine-j...@googlegroups.com.
To unsubscribe from this group, send email to 
google-appengine-java+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/google-appengine-java?hl=en.

Re: [appengine-java] Re: Google Plugin for Eclipse 1.3 plans

[Keith Platfoot]

Hi Marcel,

The Eclipse plugin has a different release cycle than the App Engine SDK, so
no, the current plugin version remains 1.2.  Look the 1.3 version of the
plugin to be released in March (with a preview build available near the end
of this month).

Keith

On Thu, Feb 11, 2010 at 9:09 AM, Marcel Overdijk
wrote:

> SDK 1.3.1 was released today, so I was wondering if the 1.3 plugin is
> also released, and more importantly if it contains better support for
> maven as described in Keith's post.
>
> On Feb 9, 10:11 pm, Hannu Leinonen  wrote:
> > Allright,
> >
> > As I've stated before on the list, Maven + GAE Eclipse plugin
> > integration is already possible! Exact instructions can be found in my
> > blog post athttp://
> hamandeggs.wordpress.com/2010/01/26/how-to-gae-eclipse-maven/I
> > also have made an archetype for such a project. I'm currently using
> > pretty much the same configuration in one of my projects and it works
> > quite well (only downside being that you're required to clean the
> > project on every Eclipse startup).
> >
> > Just type:
> > mvn org.apache.maven.plugins:maven-archetype-plugin:2.0-alpha-4:generate
> \
> >   -DarchetypeGroupId=org.beardedgeeks \
> >   -DarchetypeArtifactId=gae-eclipse-maven-archetype \
> >   -DarchetypeVersion=1.1.1 \
> >
> > -DarchetypeRepository=
> http://beardedgeeks.googlecode.com/svn/repository/releases
> >
> > -Hannu
> >
> > On 8.2.2010 20:35, Jake wrote:
> >
> >
> >
> > > I'm hoping for a good way to resolve workspace dependencies in
> > > Eclipse.  The m2eclipse plugin does this well, but that doesn't play
> > > nicely with the maven-war-plugin, so it doesn't work for GAE.  Running
> > > a Maven Install on each workspace dependency before deploying,
> > > however, is still nicer than having to manually generate/copy jar
> > > files.  I'm pretty new to Eclipse/Maven/GAE, so I don't know if it's
> > > possible, but I'm hopeful! :)
> >
> > > Jake
> >
> > > On Feb 6, 12:40 pm, 杨浩  wrote:
> > >> Where's the lastest plugin update sites for GAE Plugin?
> > >> I will to test it!
> >
> > >> 2010/2/6 Philippe Marschall 
> >
> > >>> Sounds like a good start. Ideally the maven eclipse plugin [1] could
> > >>> be configured to automatically generate the configuration for the
> > >>> Google Plugin and M2Eclipse [2] picking that up as well. Also an
> > >>> archetype would help quick starting. I assume you're aware that you
> > >>> get the most benefit out of that only when there are up to date Maven
> > >>> artifacts wit good metadata in a publicly available repo, preferably
> > >>> Maven central.
> >
> > >>>  [1]http://maven.apache.org/eclipse-plugin.html
> > >>>  [2]http://m2eclipse.sonatype.org/
> >
> > >>> Cheers
> > >>> Philippe
>
> --
> You received this message because you are subscribed to the Google Groups
> "Google App Engine for Java" group.
> To post to this group, send email to
> google-appengine-j...@googlegroups.com.
> To unsubscribe from this group, send email to
> google-appengine-java+unsubscr...@googlegroups.com
> .
> For more options, visit this group at
> http://groups.google.com/group/google-appengine-java?hl=en.
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine for Java" group.
To post to this group, send email to google-appengine-j...@googlegroups.com.
To unsubscribe from this group, send email to 
google-appengine-java+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/google-appengine-java?hl=en.

Re: [appengine-java] Re: Google Plugin for Eclipse 1.3 plans

[Rajeev Dayal]

Can you provide a stack trace?

On Thu, Feb 11, 2010 at 1:29 PM, Sudhir  wrote:

> Has anyone else noticed that installing GAE SDK 1.3.1 screws up the
> Google Plugin? It keeps throwing class loader exceptions and renders
> the run configs useless.
>
> On Feb 11, 9:23 pm, Keith Platfoot  wrote:
> > Hi Marcel,
> >
> > The Eclipse plugin has a different release cycle than the App Engine SDK,
> so
> > no, the current plugin version remains 1.2.  Look the 1.3 version of the
> > plugin to be released in March (with a preview build available near the
> end
> > of this month).
> >
> > Keith
> >
> > On Thu, Feb 11, 2010 at 9:09 AM, Marcel Overdijk
> > wrote:
> >
> >
> >
> > > SDK 1.3.1 was released today, so I was wondering if the 1.3 plugin is
> > > also released, and more importantly if it contains better support for
> > > maven as described in Keith's post.
> >
> > > On Feb 9, 10:11 pm, Hannu Leinonen  wrote:
> > > > Allright,
> >
> > > > As I've stated before on the list, Maven + GAE Eclipse plugin
> > > > integration is already possible! Exact instructions can be found in
> my
> > > > blog post athttp://
> > > hamandeggs.wordpress.com/2010/01/26/how-to-gae-eclipse-maven/I
> > > > also have made an archetype for such a project. I'm currently using
> > > > pretty much the same configuration in one of my projects and it works
> > > > quite well (only downside being that you're required to clean the
> > > > project on every Eclipse startup).
> >
> > > > Just type:
> > > > mvn
> org.apache.maven.plugins:maven-archetype-plugin:2.0-alpha-4:generate
> > > \
> > > >   -DarchetypeGroupId=org.beardedgeeks \
> > > >   -DarchetypeArtifactId=gae-eclipse-maven-archetype \
> > > >   -DarchetypeVersion=1.1.1 \
> >
> > > > -DarchetypeRepository=
> > >http://beardedgeeks.googlecode.com/svn/repository/releases
> >
> > > > -Hannu
> >
> > > > On 8.2.2010 20:35, Jake wrote:
> >
> > > > > I'm hoping for a good way to resolve workspace dependencies in
> > > > > Eclipse.  The m2eclipse plugin does this well, but that doesn't
> play
> > > > > nicely with the maven-war-plugin, so it doesn't work for GAE.
>  Running
> > > > > a Maven Install on each workspace dependency before deploying,
> > > > > however, is still nicer than having to manually generate/copy jar
> > > > > files.  I'm pretty new to Eclipse/Maven/GAE, so I don't know if
> it's
> > > > > possible, but I'm hopeful! :)
> >
> > > > > Jake
> >
> > > > > On Feb 6, 12:40 pm, 杨浩  wrote:
> > > > >> Where's the lastest plugin update sites for GAE Plugin?
> > > > >> I will to test it!
> >
> > > > >> 2010/2/6 Philippe Marschall 
> >
> > > > >>> Sounds like a good start. Ideally the maven eclipse plugin [1]
> could
> > > > >>> be configured to automatically generate the configuration for the
> > > > >>> Google Plugin and M2Eclipse [2] picking that up as well. Also an
> > > > >>> archetype would help quick starting. I assume you're aware that
> you
> > > > >>> get the most benefit out of that only when there are up to date
> Maven
> > > > >>> artifacts wit good metadata in a publicly available repo,
> preferably
> > > > >>> Maven central.
> >
> > > > >>>  [1]http://maven.apache.org/eclipse-plugin.html
> > > > >>>  [2]http://m2eclipse.sonatype.org/
> >
> > > > >>> Cheers
> > > > >>> Philippe
> >
> > > --
> > > You received this message because you are subscribed to the Google
> Groups
> > > "Google App Engine for Java" group.
> > > To post to this group, send email to
> > > google-appengine-j...@googlegroups.com.
> > > To unsubscribe from this group, send email to
> > > google-appengine-java+unsubscr...@googlegroups.com unsubscr...@googlegroups.com>
> > > .
> > > For more options, visit this group at
> > >http://groups.google.com/group/google-appengine-java?hl=en.
>
> --
> You received this message because you are subscribed to the Google Groups
> "Google App Engine for Java" group.
> To post to this group, send email to
> google-appengine-j...@googlegroups.com.
> To unsubscribe from this group, send email to
> google-appengine-java+unsubscr...@googlegroups.com
> .
> For more options, visit this group at
> http://groups.google.com/group/google-appengine-java?hl=en.
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine for Java" group.
To post to this group, send email to google-appengine-j...@googlegroups.com.
To unsubscribe from this group, send email to 
google-appengine-java+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/google-appengine-java?hl=en.

Re: [appengine-java] Re: Google Plugin for Eclipse 1.3 plans

[Miguel Méndez]

It has not been released yet.  We expect the preview to be available around
the end of the month.  We'll send out an announcement when it is ready.

On Tue, Feb 16, 2010 at 11:47 PM, KasperDK  wrote:

> Hi all,
>
> Where exactly is the Google Plugin for Eclipse preview located ? Or is
> it not released yet ? Im dying to try it out :-)
>
> Cheers,
>
> :-) Kasper
>
> On Feb 4, 8:52 pm, Keith Platfoot  wrote:
> > Hey all,
> >
> > Many of you have reported incompatibilities between the Google Plugin for
> > Eclipse and other build systems/project structures, most notably Maven
> and
> > J2EE/Dynamic Web Projects.  For example, issue 1515 (Eclipse plugin
> requires
> > fixed location for war
> > directory)<
> http://code.google.com/p/googleappengine/issues/detail?id=1515>
> > has
> > collected well over 100 stars, and a similar one in the GWT issue tracker
> > has attracted a lot of attention as well.  Based on this feedback, we've
> > decided to try and address as many of the incompatibilities as possible
> with
> > our upcoming 1.3 release of the plugin.  To deliver on that goal, we want
> to
> > share with your our current plans, and also let you know about a preview
> > build that we'll make available so you can test the changes for yourself
> and
> > give us feedback before final release.
> >
> > Our plans for the 1.3 release include 4 changes designed to make
> integration
> > with Maven and J2EE projects easier:
> >
> >1. The WAR directory can now be configured to be *any*
> project-relative
> >path (e.g. src/main/webapp if you're using Maven).  You'll also be
> able
> >to specify whether that directory is source-only (typical Maven/J2EE
> >scenario), or whether it should also function as the WAR output
> directory
> >from which to run/debug or deploy to App Engine.  If your WAR
> directory is
> >input *and* output (which will remain the default for new Web App
> >projects), the plugin will manage synchronizing the contents of
> WEB-INF/lib
> >WEB-INF/classes with your project's build path and compiled output.
> > Otherwise, we'll leave your WAR source directory alone and you'll
> need to
> >specify your WAR output location when launching, deploying, etc (the
> plugin
> >will remember the location once you set it the first time).
> >2. The Web App launch configuration UI is being redesigned to allow
> you
> >to see, and if necessary change, *any* of the launch arguments.
> > Previously, we were waiting until launch time to set many of these
> >arguments based on heuristics that were invisible and inaccessible to
> you.
> > Now you'll be in full control of how your projects get launched.
>  Also,
> >we're adding the capability to automatically migrate your launch
> >configurations when necessary, for example, updating the -javaagent
> flag
> >when changing App Engine SDKs.
> >3. GWT/App Engine projects will no longer require our SDK library on
> the
> >classpath.  This means Maven users will be able to pull in JAR files
> from
> >their M2 repository as they're accustomed to and the plugin won't mind
> a
> >bit.
> >4. The severity of any problem marker generated by the plugin will be
> >fully customizable via an Errors/Warnings preference page (similar to
> the
> >Java Errors/Warnings page), letting you specify either Error, Warning,
> or
> >Ignore.
> >
> > We'll also be including a few smaller features and bug fixes as well.
> >
> > What does everyone think about the 4 changes outlined above?  We've been
> > testing the plugin against various Maven and J2EE configurations to try
> to
> > ensure that we've eliminated the most critical roadblocks.  However,
> we're
> > very interested in also having you folks take it for a spin before the
> > official release date (slated for next month).  We're not quite ready
> yet,
> > but stay tuned for a 1.3 preview build to be made available hopefully in
> a
> > few weeks.  We'll distribute it as a zip file for dropin
> > installation
> > so
> > it will come with the standard warnings and caveats (use with a clean
> > Eclipse install and workspace, use at your risk, etc.).  However, it will
> > hopefully give you a chance to give us any last-minute feedback about our
> > changes before the final release.
> >
> > Thanks,
> >
> > Keith
>
> --
> You received this message because you are subscribed to the Google Groups
> "Google App Engine for Java" group.
> To post to this group, send email to
> google-appengine-j...@googlegroups.com.
> To unsubscribe from this group, send email to
> google-appengine-java+unsubscr...@googlegroups.com
> .
> For more options, visit this group at
> http://groups.google.com/group/google-appengine-java?hl=en.
>
>


-- 
Miguel

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine for Java" group.
To post to this group, send email to go

Re: [appengine-java] Re: Google Plugin for Eclipse 1.3 plans

[Keith Platfoot]

In case anyone on this thread missed announcement, the Google Plugin for
Eclipse 1.3 preview is now available:

http://groups.google.com/group/google-appengine-java/browse_thread/thread/460417b76e30c366/a7d8a913ef023878

Keith

2010/2/17 Miguel Méndez 

> It has not been released yet.  We expect the preview to be available around
> the end of the month.  We'll send out an announcement when it is ready.
>
>
> On Tue, Feb 16, 2010 at 11:47 PM, KasperDK  wrote:
>
>> Hi all,
>>
>> Where exactly is the Google Plugin for Eclipse preview located ? Or is
>> it not released yet ? Im dying to try it out :-)
>>
>> Cheers,
>>
>> :-) Kasper
>>
>> On Feb 4, 8:52 pm, Keith Platfoot  wrote:
>> > Hey all,
>> >
>> > Many of you have reported incompatibilities between the Google Plugin
>> for
>> > Eclipse and other build systems/project structures, most notably Maven
>> and
>> > J2EE/Dynamic Web Projects.  For example, issue 1515 (Eclipse plugin
>> requires
>> > fixed location for war
>> > directory)<
>> http://code.google.com/p/googleappengine/issues/detail?id=1515>
>> > has
>> > collected well over 100 stars, and a similar one in the GWT issue
>> tracker
>> > has attracted a lot of attention as well.  Based on this feedback, we've
>> > decided to try and address as many of the incompatibilities as possible
>> with
>> > our upcoming 1.3 release of the plugin.  To deliver on that goal, we
>> want to
>> > share with your our current plans, and also let you know about a preview
>> > build that we'll make available so you can test the changes for yourself
>> and
>> > give us feedback before final release.
>> >
>> > Our plans for the 1.3 release include 4 changes designed to make
>> integration
>> > with Maven and J2EE projects easier:
>> >
>> >1. The WAR directory can now be configured to be *any*
>> project-relative
>> >path (e.g. src/main/webapp if you're using Maven).  You'll also be
>> able
>> >to specify whether that directory is source-only (typical Maven/J2EE
>> >scenario), or whether it should also function as the WAR output
>> directory
>> >from which to run/debug or deploy to App Engine.  If your WAR
>> directory is
>> >input *and* output (which will remain the default for new Web App
>> >projects), the plugin will manage synchronizing the contents of
>> WEB-INF/lib
>> >WEB-INF/classes with your project's build path and compiled output.
>> > Otherwise, we'll leave your WAR source directory alone and you'll
>> need to
>> >specify your WAR output location when launching, deploying, etc (the
>> plugin
>> >will remember the location once you set it the first time).
>> >2. The Web App launch configuration UI is being redesigned to allow
>> you
>> >to see, and if necessary change, *any* of the launch arguments.
>> > Previously, we were waiting until launch time to set many of these
>> >arguments based on heuristics that were invisible and inaccessible to
>> you.
>> > Now you'll be in full control of how your projects get launched.
>>  Also,
>> >we're adding the capability to automatically migrate your launch
>> >configurations when necessary, for example, updating the -javaagent
>> flag
>> >when changing App Engine SDKs.
>> >3. GWT/App Engine projects will no longer require our SDK library on
>> the
>> >classpath.  This means Maven users will be able to pull in JAR files
>> from
>> >their M2 repository as they're accustomed to and the plugin won't
>> mind a
>> >bit.
>> >4. The severity of any problem marker generated by the plugin will be
>> >fully customizable via an Errors/Warnings preference page (similar to
>> the
>> >Java Errors/Warnings page), letting you specify either Error,
>> Warning, or
>> >Ignore.
>> >
>> > We'll also be including a few smaller features and bug fixes as well.
>> >
>> > What does everyone think about the 4 changes outlined above?  We've been
>> > testing the plugin against various Maven and J2EE configurations to try
>> to
>> > ensure that we've eliminated the most critical roadblocks.  However,
>> we're
>> > very interested in also having you folks take it for a spin before the
>> > official release date (slated for next month).  We're not quite ready
>> yet,
>> > but stay tuned for a 1.3 preview build to be made available hopefully in
>> a
>> > few weeks.  We'll distribute it as a zip file for dropin
>> > installation
>> > so
>> > it will come with the standard warnings and caveats (use with a clean
>> > Eclipse install and workspace, use at your risk, etc.).  However, it
>> will
>> > hopefully give you a chance to give us any last-minute feedback about
>> our
>> > changes before the final release.
>> >
>> > Thanks,
>> >
>> > Keith
>>
>> --
>> You received this message because you are subscribed to the Google Groups
>> "Google App Engine for Java" group.
>> To post to this group, send email to
>> google-appengine-j...@googlegroups