Re: [wtp-dev] Jakarta EE LSP for Eclipse IDE (WTP)

[Fred Bricon]

Le ven. 4 sept. 2020 à 08:19, Jean-Francois Maury  a
écrit :

> My team has started a couple of initiatives around WTP (RSP protocol) ,
> Microprofile (Quarkus Eclipse tooling).that are linked to LSP.
>

Actually we contributed that Microprofile Language Server to Eclipse:
https://github.com/eclipse/lsp4mp

So we can help around the Eclipse integration.
>
>
>
> On Thu, Sep 3, 2020 at 10:39 PM Kevin Sutter  wrote:
>
>> Hi,
>> Before we get into the technical question... How does one go about
>> registering another email address on this mailing list?  I tried sending a
>> note to wtp-dev-subscr...@eclipse.org and it got rejected (this has
>> worked with all of the EE4J mailing lists...).
>>
>> My real question is...  We're working with some University students to
>> possibly develop a Language Server for the Jakarta EE 9 API.  We've done a
>> similar effort with MicroProfile API and it's advancing quite well.
>>
>> Here's the description of the project:
>>
>> https://canosp.ca/2020/08/10/f20-projects/#language-server-for-eclipse-jakarta-ee
>>
>> I'm not aware of any activity by the WTP project in this arena of
>> supporting Jakarta EE. If I'm wrong about this, please let me know.
>> Otherwise, I'm hoping that this type of project would be of interest to the
>> WTP team.  Would there be enough interest to possibly even help mentor this
>> project?
>>
>> We've got some basic questions relating to the github repo.  Should we
>> start with private repos?  Is there a WTP "sandbox" repo that we could
>> start with?  Or, do we need to create an Eclipse project?  Eventually, we
>> may also need some assistance with developing the LSP client for Eclipse.
>>
>> Any input, suggestions, comments would be appreciated.  Thanks!
>> -- Kevin Sutter
>> Jakarta EE 9 Release Lead
>> ___
>> wtp-dev mailing list
>> wtp-dev@eclipse.org
>> To unsubscribe from this list, visit
>> https://www.eclipse.org/mailman/listinfo/wtp-dev
>>
>
>
> --
>
> Jeff Maury
>
> Manager, DevTools
>
> Red Hat EMEA 
>
> jma...@redhat.com
> @RedHat    Red Hat
>   Red Hat
> 
> 
> 
> ___
> wtp-dev mailing list
> wtp-dev@eclipse.org
> To unsubscribe from this list, visit
> https://www.eclipse.org/mailman/listinfo/wtp-dev
>
___
wtp-dev mailing list
wtp-dev@eclipse.org
To unsubscribe from this list, visit 
https://www.eclipse.org/mailman/listinfo/wtp-dev

Re: [wtp-dev] Development Status meeting reminder

[Fred Bricon]

Hi Carl,

I'll try to join the call to discuss https://bugs.eclipse.org/514672

Fred

On Thu, Apr 6, 2017 at 1:17 PM, Carl Anderson  wrote:

> Folks,
>
> Just a reminder that there will be a Web Tools Platform Development Status
> Meeting today (4/6)- the agenda has already been posted at
> https://wiki.eclipse.org/WTP_2017-04-06 - feel free to add more.
>
> Sincerely,
>
> - Carl Anderson
> WTP PMC lead
>
> ___
> wtp-dev mailing list
> wtp-dev@eclipse.org
> To change your delivery options, retrieve your password, or unsubscribe
> from this list, visit
> https://dev.eclipse.org/mailman/listinfo/wtp-dev
>



-- 
"Have you tried turning it off and on again" - The IT Crowd
And if that fails, then http://goo.gl/tnBgH5
___
wtp-dev mailing list
wtp-dev@eclipse.org
To change your delivery options, retrieve your password, or unsubscribe from 
this list, visit
https://dev.eclipse.org/mailman/listinfo/wtp-dev

Re: [wtp-dev] JSDT Sync call minutes [20160112]

[Fred Bricon]

m2e tests simply don't live @ eclipse.org

It was deemed too complex/tedious to try to CQ the sheer number of
dependencies that are dragged while running tests (all these files are
stored in the git repo to speed up test execution).

So tests live in github https://github.com/tesla/m2e-core-tests and run on
an external CI server
https://ci.takari.io/view/m2e/job/m2eclipse-core-tests/

This is less than ideal, obviously, I'd prefer if we could have all code
and run all tests on the same infra, but I just can't imagine having to
open ~400 CQs (it'd be probably forbidden upon by the Geneva convention)

Fred




On Wed, Jan 13, 2016 at 3:45 PM, Chuck Bridgham  wrote:

> Regarding the testing restrictions downloading dependencies via npm or
> bower..I wonder what m2e(Maven) does for tests? because this is a
> similar repository issue?
>
> ccing Fred on this.
>
> Thanks - Chuck
>
> IBM Tools development, Eclipse WTP PMC
> IBM Software Lab - Research Triangle Park, NC
>
>
>
> From:"Victor V. Rubezhny" 
> To:wtp-dev@eclipse.org
> Date:01/13/2016 12:57 PM
> Subject:Re: [wtp-dev] JSDT Sync call minutes [20160112]
> Sent by:wtp-dev-boun...@eclipse.org
> --
>
>
>
> +1 from me too, but...
>
> Yes, I've asked not to include any JUnit tests into the contribution.
> Otherwise I have had to open a number of additional CQs for those tests,
> while we are limited in time.
>
> Any JUnit Tests which aren't bringing a licensing problems are welcomed
> and can be added at any time after the contribution is done.
>
> There is a couple of little licensing problems regarding these tests:
> 1) any json file (like bower.json, for example) is to be written by a
> committer or a contributor (we must respect authors) - I think it's the
> smallest problem.
> 2) bower.json and package.json files specify dependencies for a project,
> but we have no our own projects in bower/npm repositories published under
> Eclipse Public License, so it's very problematic for us to reference any
> products (in these files) in our tests. At least I don't know a single
> existing javascript library published under EPL in npm. The same problem is
> for Bower/NPM tools contributed by Ilya.
>
> So, we CAN write some common JUnit tests for testing some functionality,
> like creating some json file, finding content assist proposals according to
> its JSON Schema, validating it against the schema, but we CANNOT use a json
> file to download any dependency into a test project or, for example, to
> show proposals of possible versions of some javascript library (because it
> requires us to download it from outside of Eclipse's repositories) and/or
> request any info from bower or npm repositories.
>
> As far as I understood, we have to open a CQ every time we need to use
> something "from outside" in case we're not sure that it's license allows us
> to do it from Eclipse.
>
> Ilya has some JUnit tests for bower/npm tools - but those tests don't
> download anything afaik. So, if we have some tests which aren't using a
> content not authored by a contributor (Angelo or the other ones) or a
> committer - we CAN push such tests into Source Editing repo. Otherwise we
> have to open a CQ for every file or a library to be used and/or downloaded
> by JUnit test during its work.
>
> In most cases there are no problems to open a CQ... It just takes to long
> to resolve sometimes.
>
> Regards,
> Victor
>
>
>
> On 01/13/2016 11:29 AM, Mickael Istria wrote:
> On 01/13/2016 09:23 AM, Angelo zerr wrote:
> I think it should be very good to integrate JUnit tests
> 
> *https://github.com/angelozerr/eclipse-wtp-json/tree/master/core/org.eclipse.wst.json.core.tests*
> that
> I have not included in the gerrit patch (Victor told me to remove it).
> +1.
> Unless there are complex legal issues with those, can you please turn them
> as a patch to webtools.sourceediting and push it onto Gerrit?
>
> --
> Mickael Istria
> Eclipse developer at *JBoss, by Red Hat* 
> *My blog*  - *My Tweets*
> 
>
>
> ___
> wtp-dev mailing list
> *wtp-dev@eclipse.org* 
> To change your delivery options, retrieve your password, or unsubscribe
> from this list, visit
> *https://dev.eclipse.org/mailman/listinfo/wtp-dev*
> 
>
> CONFIDENTIALITY NOTICE: This email and files attached to it are
> confidential. If you are not the intended recipient you are hereby notified
> that using, copying, distributing or taking any action in reliance on the
> contents of this information is strictly prohibited. If you 

Re: [wtp-dev] JSDT Sync call minutes [20160112]

[Fred Bricon]

Right, according to
https://wiki.eclipse.org/Development_Resources/IP/Test_and_Build_Dependencies

But it also says "*Test-only dependencies must not be checked into Eclipse
SCM in any form*" which doesn't work for m2e. Anyways, I don't want to
highjack the JSDT thread with m2e specific issues. I'll try to follow up on
that matter when I get spare cycles.

Fred



On Wed, Jan 13, 2016 at 4:44 PM, Mike Milinkovich <
mike.milinkov...@eclipse.org> wrote:

> On 13/01/2016 4:13 PM, Fred Bricon wrote:
>
>> This is less than ideal, obviously, I'd prefer if we could have all code
>> and run all tests on the same infra, but I just can't imagine having to
>> open ~400 CQs (it'd be probably forbidden upon by the Geneva convention)
>>
>
> Perhaps I am misunderstanding this thread, but to me these tests sound
> like Build and Test dependencies. I am pretty sure that you can file one CQ
> for all the test dependencies and you're done.
>
> --
> Mike Milinkovich
> mike.milinkov...@eclipse.org
> +1.613.220.3223 (mobile)
>
>
> ___
> wtp-dev mailing list
> wtp-dev@eclipse.org
> To change your delivery options, retrieve your password, or unsubscribe
> from this list, visit
> https://dev.eclipse.org/mailman/listinfo/wtp-dev
>



-- 
"Have you tried turning it off and on again" - The IT Crowd
And if that fails, then http://goo.gl/tnBgH5
___
wtp-dev mailing list
wtp-dev@eclipse.org
To change your delivery options, retrieve your password, or unsubscribe from 
this list, visit
https://dev.eclipse.org/mailman/listinfo/wtp-dev

[m2e-wtp-dev] m2e 1.7.0 M3 is available

[Fred Bricon]

Hello World,

m2e 1.7.0 (1.7.0.20151110-2248) M3 for Neon is now available. It can be
installed from [1].
Highlights of this release include
- maven archetype plugin updated to 2.4
- Maven Launch configurations now use the PROJECT_LOC variable expression,
instead of absolute paths, making launch configurations portable across
workspaces by default. Many thanks to Konrad Windszus for his
contribution[2].

The rest of the bug fixes[3] are mainly corrections for disposed widgets,
reported by AERI, Eclipse's Automatic bug reporting tool.

Enjoy,

Fred.

[1] http://download.eclipse.org/technology/m2e/milestones/1.7/
[2] https://bugs.eclipse.org/bugs/show_bug.cgi?id=343026
[3]
https://bugs.eclipse.org/bugs/buglist.cgi?bug_status=RESOLVED_status=VERIFIED_status=CLOSED=m2e_format=advanced=FIXED_milestone=1.7.0%2FNeon%20M3


-- 
"Have you tried turning it off and on again" - The IT Crowd
And if that fails, then http://goo.gl/tnBgH5
___
m2e-wtp-dev mailing list
m2e-wtp-dev@eclipse.org
To change your delivery options, retrieve your password, or unsubscribe from 
this list, visit
https://dev.eclipse.org/mailman/listinfo/m2e-wtp-dev

Re: [m2e-wtp-dev] m2e 1.6.2 RC1 and m2e 1.7.0 M1 are available

[Fred Bricon]

Hi,

I re-spun the staged 1.6.2 and 1.7.0 RCs in order to include a fix for [1].
New builds are now 1.6.2.20150819-1555 and 1.7.0.20150819-1552.

Sorry for the inconvenience.

[1] https://bugs.eclipse.org/471843

Fred

On Tue, Aug 18, 2015 at 10:02 PM, Fred Bricon fbri...@gmail.com wrote:

 Hello World,

 m2e 1.6.2 (1.6.2.20150818-2354) RC1 for Mars has been released. It notably
 fixes a regression introduced in 1.6.1 that broke the groovy configurator.
 See the changelog here [1]. It can be installed from [2]. 3rd party
 configurator providers are *strongly* encouraged to check 1.6.2 works for
 them.
 Unless new blocking issues are found for m2e 1.6.2.20150818-2354, it will
 most likely be released as-is next week.

 m2e 1.7.0 (1.7.0.20150818-2353) M1 for Neon includes all the fixes from
 1.6.2 plus initial Java 9 support [3]. It can be installed from [4].
 Java 9 beta support for Eclipse must be installed from the Marketplace[5].
 Please note m2e 1.7.0 now requires JDK 8 minimum to run.

 Enjoy,

 Fred.

 [1]
 https://bugs.eclipse.org/bugs/buglist.cgi?bug_status=RESOLVEDbug_status=VERIFIEDbug_status=CLOSEDlist_id=12449669product=m2equery_format=advancedresolution=FIXEDtarget_milestone=1.6.2%2FMars%20RC1
 [2] http://download.eclipse.org/technology/m2e/milestones/1.6/
 [3]
 https://bugs.eclipse.org/bugs/buglist.cgi?bug_status=RESOLVEDbug_status=VERIFIEDbug_status=CLOSEDlist_id=12449669product=m2equery_format=advancedresolution=FIXEDtarget_milestone=1.7.0%2FNeon%20M1
 [4] http://download.eclipse.org/technology/m2e/milestones/1.7/
 [5] https://www.eclipse.org/mars/noteworthy/#_java_9_beta


 --
 Have you tried turning it off and on again - The IT Crowd
 And if that fails, then http://goo.gl/tnBgH5




-- 
Have you tried turning it off and on again - The IT Crowd
And if that fails, then http://goo.gl/tnBgH5
___
m2e-wtp-dev mailing list
m2e-wtp-dev@eclipse.org
To change your delivery options, retrieve your password, or unsubscribe from 
this list, visit
https://dev.eclipse.org/mailman/listinfo/m2e-wtp-dev

[wtp-dev] Can we drop the JOnAS v4 adapter from WTP?

[Fred Bricon]

Hello world,

is there any reason why we're keeping the old JOnAS v4 server adapter in
WTP?
We dropped the old JBoss some time ago, because JBoss Tools provides much
better adapters.

I see that JOPE[1], supporting JOnAS v4 and v5, is available from the
Download additional server adapters link, in the new Server wizard.
Even though it doesn't hurt to keep it in WTP, JOnAS v4 really feels
irrelevant these days.

If others agree with me, I'll open a request in BZ.

[1] http://forge.ow2.org/projects/jope

Fred

-- 
Have you tried turning it off and on again - The IT Crowd
And if that fails, then http://goo.gl/tnBgH5
___
wtp-dev mailing list
wtp-dev@eclipse.org
To change your delivery options, retrieve your password, or unsubscribe from 
this list, visit
https://dev.eclipse.org/mailman/listinfo/wtp-dev

Re: [m2e-wtp-dev] [m2e-dev] Breaking changes to the archetype API - m2e 2.0?

[Fred Bricon]

Yes, exactly my point. major bump or not, due to archetyper classes
changes, that is the question.

On Thu, Mar 19, 2015 at 1:29 AM, Greg Amerson gregory.amer...@liferay.com
wrote:

 Thanks for the details Fred.  This change doesn't break our API usage
 because we just depend on some m2e-core internal APIs which don't appear to
 change with that changeset.

 Speaking of which, looking at just this one commit:
 https://github.com/fbricon/m2e-core/commit/29e014e49fb2cb442ed2f935590ad1c296a2dfe2

 For org.eclipse.m2e.core API I don't see any non-internal API changes,
 thus there is no reason here to necessitate a 1.6-2.0 jump.  That leaves
 the jars that are bundled in the maven runtime will change with the new
 archetyper 2.3 version.  So I guess that is where the 1.6-2.0 major
 version bump is required right?

 On Thu, Mar 19, 2015 at 11:39 AM, Fred Bricon fbri...@gmail.com wrote:

 Greg,

 only internal m2e classes have been modified, but the archetype runtime
 doesn't expose the same Maven classes anymore
 (org.apache.maven.archetype.Archetype - ArchetypeManager) so... it might
 not even apply for a major version bump after all. that's debatable I guess.

 Here's the extent of the changes, so far :
 https://github.com/eclipse/m2e-core/compare/master...fbricon:archetyper-2.x?expand=1

 If we can keep on with 1.6 with these changes, fine by me :-)

 The downside of moving to 2.0 is a lot of m2e extensions would probably
 need to be rebuilt if they use version ranges like [1.0, 2.0). That's
 impacts definitely more adopters than the handful that depends on the
 archetype API.


 On Wed, Mar 18, 2015 at 11:02 PM, Greg Amerson 
 gregory.amer...@liferay.com wrote:

 Hey Fred,

 Just want to clarify some of the APIs that may be changing.  In our
 adopter product we have code that looks like this:

 final ArchetypeManager archetypeManager =
 MavenPluginActivator.getDefault().getArchetypeManager();
 final ArtifactRepository remoteArchetypeRepository =
 archetypeManager.getArchetypeRepository( archetype );
 ...
 final ListIProject newProjects =
 projectConfigurationManager.createArchetypeProjects(
 location, archetype, groupId, artifactId, version,
 javaPackage, properties, configuration, monitor );


 I'm assuming you mean some of these APIs will change in incompatible
 ways in the proposed m2e 2.0?  Well I guess ArchetypeManager was always
 marked internal, so its fair game to be changed even if m2e doesn't go to
 2.0. But the IProjectConfigurationManager was API, so is that one of the
 interfaces that will undergo breaking change in 2.0?

 On Thu, Mar 19, 2015 at 10:00 AM, Jason van Zyl ja...@takari.io wrote:

 Is there any downside at all to upgrading? If you've done the work and
 fixed all those issues I'm super happy you've moved us forward.

 Honestly I doubt anyone has tied into the guts of Archetype aside from
 you and really I think it's a small price to pay if the odd party is.
 You've updated the code and I assume made it easier to deal with so I only
 see upside.

 +1

 On Mar 18, 2015, at 7:45 PM, Fred Bricon fbri...@gmail.com wrote:

  Hi,
 
  I have an initial POC that uses maven-archetype-plugin 2.3, instead
 of the 2.0.alpha4 version (which was released in the 17th century, give or
 take).
 
  I checked it fixes the following issues :
  - https://bugs.eclipse.org/459453,
  - https://bugs.eclipse.org/424010,
  - https://bugs.eclipse.org/394918,
  - https://bugs.eclipse.org/374660,
  - https://bugs.eclipse.org/405945 (on OSX at least),
  - https://bugs.eclipse.org/415114,
  - https://bugs.eclipse.org/429287
 
  Bugs https://bugs.eclipse.org/446657, https://bugs.eclipse.org/348893
 may or not be fixed (I can't test proxies)
 
  Most of these issues were automatically closed already after 1 year
 of inactivity. Doesn't mean the bugs are not there. My level of annoyance
 just reached a point where I'd like to take action now.
 
  The only problem with the archetype update is it will break 3rd party
 adopters (JBoss Tools at least) depending on the archetype API
 (package/class names changed between 2.0.alpha4 and 2.3). I don't plan on
 introducing a compatibility layer, not worth the hassle IMHO.
  Given that I'm also in charge of the JBoss Tools integration, I'm
 fine with the impact :-)
 
  Getting the fix in will require m2e to bump its version to 2.0 (and
 open a bunch of CQs  in ipzilla)
 
  I'd really like to get that change in for Eclipse Mars, if possible.
 Is it too late from a release plan standpoint (i.e. 1.6 - 2.0)? PMC,
 fellow m2e committers wdyt?
 
  Fred
 
  --
  Have you tried turning it off and on again - The IT Crowd
  ___
  m2e-dev mailing list
  m2e-...@eclipse.org
  To change your delivery options, retrieve your password, or
 unsubscribe from this list, visit
  https://dev.eclipse.org/mailman/listinfo/m2e-dev

 Thanks,

 Jason

 --
 Jason van Zyl

Re: [m2e-wtp-dev] Deploymetn Assembly needs /target/myproject.war

[Fred Bricon]

what kind of deployment are you doing? Is it something equivalent to
Tomcat's serve resources without publishing? In that case server adapters
are notoriously known to not support overlays.
Do you know exactly which resources are missing? Can you provide a sample
test project? Does it deploy on another application server (wildfly for
instance)?

On Tue, Jan 13, 2015 at 3:12 AM, Marc Schlegel my.mailing.li...@gmx.de
wrote:

 Hello everyone

 I am facing some problems with m2e-wtp regarding the deployment of a
 simple war to a WebSphere Liberty Profile 8.5.5.4.

 The problem is, that in order to deploy successfully using WTP I need to
 add the exploded WAR-folder generated by Maven (/target/myap.war) to the
 Deployment Assembly in the Eclipse project properties. When I dont do this,
 the application is deployt but I cannot access any page (404). M2E-WTP
 seems to have set all properties correctly (e.g. Deployed Resources) and
 when I export the project as WAR in Eclipse everything is there (Resources,
 Overlays, Libs, Configuration), so I don't understand why I have to add the
 maven-assembly as well?

 I am using JBoss Developer Studio 8.0.1 which comes with the latest stable
 m2e-wtp.

 regards
 Marc

 ___
 m2e-wtp-dev mailing list
 m2e-wtp-dev@eclipse.org
 To change your delivery options, retrieve your password, or unsubscribe
 from this list, visit
 https://dev.eclipse.org/mailman/listinfo/m2e-wtp-dev




-- 
Have you tried turning it off and on again - The IT Crowd
___
m2e-wtp-dev mailing list
m2e-wtp-dev@eclipse.org
To change your delivery options, retrieve your password, or unsubscribe from 
this list, visit
https://dev.eclipse.org/mailman/listinfo/m2e-wtp-dev

[m2e-wtp-dev] (Undocumented) behaviour of wb-resource publishing

[Fred Bricon]

Hello World,

m2e-wtp supports one of Maven's features known as resource filtering for
web [1] and ear [2] projects. Some files contain placeholders that are
replaced by Maven, during a build, with actual values.
Typically, we could have a web.xml file containing

web-app

context-param

 param-namejavax.faces.PROJECT_STAGE/param-name

 param-value${jsf.project.stage}/param-value

/context-param

...

/web-app

with filtering enabled and a jsf.project.stage property set to either
Development or Production in pom.xml, that would generate a (filtered)
web.xml in target/m2e-wtp/web-resources/META-INF/ like

web-app

context-param

 param-namejavax.faces.PROJECT_STAGE/param-name

 param-valueDevelopment/param-value

/context-param

...

/web-app

A similar mechanism exists to filter resources in EAR projects, where
filtered resources end up under  target/m2e-wtp/ear-resources/.

Now, in order to publish the filtered version of these files, instead of
the raw, unfiltered one, m2e-wtp relies on a kind of undocumented behaviour
: in  .settings/org.eclipse.wst.common.component, the folder containing
generated files is declared *first* :

?xml version=1.0 encoding=UTF-8?project-modules id=moduleCoreId
project-version=1.5.0

wb-module deploy-name=index-ear

wb-resource deploy-path=/ source-path=
/target/m2e-wtp/ear-resources/

wb-resource deploy-path=/ source-path=/src/main/application tag
=defaultRootSource/

 ...

/wb-module

/project-modules
So when files are duplicated in different wb-resources, the first one found
wins. At least this is true for JBoss, Tomcat, Glassfish server adapters.

Now, it turns out IBM Websphere server adapter does the opposite, last file
wins, which is a problem [3] because unfiltered files end up being served.

S, I would like the WTP to document what is the expected behaviour of
publishing conflicting resources from several wb-modules. I would relly
like to avoid adding one more hack to m2e-wtp to handle these opposite
behaviours.
Which would give us 2 options :
1 - If it's explicitely said first resource wins, then IBM will need to fix
their server adapter.
2 - If the last resource should win, then m2e-wtp and all the adapters for
these open source servers would have to be fixed

Needless to say, I'm strongly in favour of option #1 :-)

I should attend today's WTP call, if anyone wants to discuss that.

Regards,

Fred Bricon


[1]
http://maven.apache.org/plugins/maven-war-plugin/examples/adding-filtering-webresources.html
[2]
http://maven.apache.org/plugins/maven-ear-plugin/examples/filtering-sources.html
[1] https://bugs.eclipse.org/437441

-- 
Have you tried turning it off and on again - The IT Crowd
___
m2e-wtp-dev mailing list
m2e-wtp-dev@eclipse.org
To change your delivery options, retrieve your password, or unsubscribe from 
this list, visit
https://dev.eclipse.org/mailman/listinfo/m2e-wtp-dev

Re: [m2e-wtp-dev] (Undocumented) behaviour of wb-resource publishing

[Fred Bricon]

Following today's call, I've opened
https://bugs.eclipse.org/bugs/show_bug.cgi?id=448544

Regards,

Fred Bricon

On Thu, Oct 23, 2014 at 1:03 PM, Fred Bricon fbri...@gmail.com wrote:

 Hello World,

 m2e-wtp supports one of Maven's features known as resource filtering for
 web [1] and ear [2] projects. Some files contain placeholders that are
 replaced by Maven, during a build, with actual values.
 Typically, we could have a web.xml file containing

 web-app

 context-param

  param-namejavax.faces.PROJECT_STAGE/param-name

  param-value${jsf.project.stage}/param-value

 /context-param

 ...

 /web-app

 with filtering enabled and a jsf.project.stage property set to either
 Development or Production in pom.xml, that would generate a (filtered)
 web.xml in target/m2e-wtp/web-resources/META-INF/ like

 web-app

 context-param

  param-namejavax.faces.PROJECT_STAGE/param-name

  param-valueDevelopment/param-value

 /context-param

 ...

 /web-app

 A similar mechanism exists to filter resources in EAR projects, where
 filtered resources end up under  target/m2e-wtp/ear-resources/.

 Now, in order to publish the filtered version of these files, instead of
 the raw, unfiltered one, m2e-wtp relies on a kind of undocumented behaviour
 : in  .settings/org.eclipse.wst.common.component, the folder containing
 generated files is declared *first* :

 ?xml version=1.0 encoding=UTF-8?project-modules id=moduleCoreId
 project-version=1.5.0

 wb-module deploy-name=index-ear

 wb-resource deploy-path=/ source-path=
 /target/m2e-wtp/ear-resources/

 wb-resource deploy-path=/ source-path=/src/main/application
 tag=defaultRootSource/

  ...

 /wb-module

 /project-modules
 So when files are duplicated in different wb-resources, the first one
 found wins. At least this is true for JBoss, Tomcat, Glassfish server
 adapters.

 Now, it turns out IBM Websphere server adapter does the opposite, last
 file wins, which is a problem [3] because unfiltered files end up being
 served.

 S, I would like the WTP to document what is the expected behaviour of
 publishing conflicting resources from several wb-modules. I would relly
 like to avoid adding one more hack to m2e-wtp to handle these opposite
 behaviours.
 Which would give us 2 options :
 1 - If it's explicitely said first resource wins, then IBM will need to
 fix their server adapter.
 2 - If the last resource should win, then m2e-wtp and all the adapters for
 these open source servers would have to be fixed

 Needless to say, I'm strongly in favour of option #1 :-)

 I should attend today's WTP call, if anyone wants to discuss that.

 Regards,

 Fred Bricon


 [1]
 http://maven.apache.org/plugins/maven-war-plugin/examples/adding-filtering-webresources.html
 [2]
 http://maven.apache.org/plugins/maven-ear-plugin/examples/filtering-sources.html
 [1] https://bugs.eclipse.org/437441

 --
 Have you tried turning it off and on again - The IT Crowd




-- 
Have you tried turning it off and on again - The IT Crowd
___
m2e-wtp-dev mailing list
m2e-wtp-dev@eclipse.org
To change your delivery options, retrieve your password, or unsubscribe from 
this list, visit
https://dev.eclipse.org/mailman/listinfo/m2e-wtp-dev

[wtp-dev] (Undocumented) behaviour of wb-resource publishing

[Fred Bricon]

Hello World,

m2e-wtp supports one of Maven's features known as resource filtering for
web [1] and ear [2] projects. Some files contain placeholders that are
replaced by Maven, during a build, with actual values.
Typically, we could have a web.xml file containing

web-app

context-param

 param-namejavax.faces.PROJECT_STAGE/param-name

 param-value${jsf.project.stage}/param-value

/context-param

...

/web-app

with filtering enabled and a jsf.project.stage property set to either
Development or Production in pom.xml, that would generate a (filtered)
web.xml in target/m2e-wtp/web-resources/META-INF/ like

web-app

context-param

 param-namejavax.faces.PROJECT_STAGE/param-name

 param-valueDevelopment/param-value

/context-param

...

/web-app

A similar mechanism exists to filter resources in EAR projects, where
filtered resources end up under  target/m2e-wtp/ear-resources/.

Now, in order to publish the filtered version of these files, instead of
the raw, unfiltered one, m2e-wtp relies on a kind of undocumented behaviour
: in  .settings/org.eclipse.wst.common.component, the folder containing
generated files is declared *first* :

?xml version=1.0 encoding=UTF-8?project-modules id=moduleCoreId
project-version=1.5.0

wb-module deploy-name=index-ear

wb-resource deploy-path=/ source-path=
/target/m2e-wtp/ear-resources/

wb-resource deploy-path=/ source-path=/src/main/application tag
=defaultRootSource/

 ...

/wb-module

/project-modules
So when files are duplicated in different wb-resources, the first one found
wins. At least this is true for JBoss, Tomcat, Glassfish server adapters.

Now, it turns out IBM Websphere server adapter does the opposite, last file
wins, which is a problem [3] because unfiltered files end up being served.

S, I would like the WTP to document what is the expected behaviour of
publishing conflicting resources from several wb-modules. I would relly
like to avoid adding one more hack to m2e-wtp to handle these opposite
behaviours.
Which would give us 2 options :
1 - If it's explicitely said first resource wins, then IBM will need to fix
their server adapter.
2 - If the last resource should win, then m2e-wtp and all the adapters for
these open source servers would have to be fixed

Needless to say, I'm strongly in favour of option #1 :-)

I should attend today's WTP call, if anyone wants to discuss that.

Regards,

Fred Bricon


[1]
http://maven.apache.org/plugins/maven-war-plugin/examples/adding-filtering-webresources.html
[2]
http://maven.apache.org/plugins/maven-ear-plugin/examples/filtering-sources.html
[1] https://bugs.eclipse.org/437441

-- 
Have you tried turning it off and on again - The IT Crowd
___
wtp-dev mailing list
wtp-dev@eclipse.org
To change your delivery options, retrieve your password, or unsubscribe from 
this list, visit
https://dev.eclipse.org/mailman/listinfo/wtp-dev

Re: [wtp-dev] (Undocumented) behaviour of wb-resource publishing

[Fred Bricon]

Following today's call, I've opened
https://bugs.eclipse.org/bugs/show_bug.cgi?id=448544

Regards,

Fred Bricon

On Thu, Oct 23, 2014 at 1:03 PM, Fred Bricon fbri...@gmail.com wrote:

 Hello World,

 m2e-wtp supports one of Maven's features known as resource filtering for
 web [1] and ear [2] projects. Some files contain placeholders that are
 replaced by Maven, during a build, with actual values.
 Typically, we could have a web.xml file containing

 web-app

 context-param

  param-namejavax.faces.PROJECT_STAGE/param-name

  param-value${jsf.project.stage}/param-value

 /context-param

 ...

 /web-app

 with filtering enabled and a jsf.project.stage property set to either
 Development or Production in pom.xml, that would generate a (filtered)
 web.xml in target/m2e-wtp/web-resources/META-INF/ like

 web-app

 context-param

  param-namejavax.faces.PROJECT_STAGE/param-name

  param-valueDevelopment/param-value

 /context-param

 ...

 /web-app

 A similar mechanism exists to filter resources in EAR projects, where
 filtered resources end up under  target/m2e-wtp/ear-resources/.

 Now, in order to publish the filtered version of these files, instead of
 the raw, unfiltered one, m2e-wtp relies on a kind of undocumented behaviour
 : in  .settings/org.eclipse.wst.common.component, the folder containing
 generated files is declared *first* :

 ?xml version=1.0 encoding=UTF-8?project-modules id=moduleCoreId
 project-version=1.5.0

 wb-module deploy-name=index-ear

 wb-resource deploy-path=/ source-path=
 /target/m2e-wtp/ear-resources/

 wb-resource deploy-path=/ source-path=/src/main/application
 tag=defaultRootSource/

  ...

 /wb-module

 /project-modules
 So when files are duplicated in different wb-resources, the first one
 found wins. At least this is true for JBoss, Tomcat, Glassfish server
 adapters.

 Now, it turns out IBM Websphere server adapter does the opposite, last
 file wins, which is a problem [3] because unfiltered files end up being
 served.

 S, I would like the WTP to document what is the expected behaviour of
 publishing conflicting resources from several wb-modules. I would relly
 like to avoid adding one more hack to m2e-wtp to handle these opposite
 behaviours.
 Which would give us 2 options :
 1 - If it's explicitely said first resource wins, then IBM will need to
 fix their server adapter.
 2 - If the last resource should win, then m2e-wtp and all the adapters for
 these open source servers would have to be fixed

 Needless to say, I'm strongly in favour of option #1 :-)

 I should attend today's WTP call, if anyone wants to discuss that.

 Regards,

 Fred Bricon


 [1]
 http://maven.apache.org/plugins/maven-war-plugin/examples/adding-filtering-webresources.html
 [2]
 http://maven.apache.org/plugins/maven-ear-plugin/examples/filtering-sources.html
 [1] https://bugs.eclipse.org/437441

 --
 Have you tried turning it off and on again - The IT Crowd




-- 
Have you tried turning it off and on again - The IT Crowd
___
wtp-dev mailing list
wtp-dev@eclipse.org
To change your delivery options, retrieve your password, or unsubscribe from 
this list, visit
https://dev.eclipse.org/mailman/listinfo/wtp-dev

Re: [wtp-dev] How to Add TomCat 8 support to Eclipse Keppler

[Fred Bricon]

Can WTP 3.6.0 be installed over Kepler? The original topic was to fix the
issue in Kepler


On Fri, May 9, 2014 at 7:49 PM, Larry Isaacs larry.isa...@sas.com wrote:

  Thanks for addressing this.  Sorry I overlooked that change for Tomcat
 8.  My testing was focused on running Tomcat 8.



 Cheers,

 Larry



 *From:* wtp-dev-boun...@eclipse.org [mailto:wtp-dev-boun...@eclipse.org] *On
 Behalf Of *Chuck Bridgham
 *Sent:* Friday, May 09, 2014 11:13 AM
 *To:* General discussion of project-wide or architectural issues.
 *Subject:* Re: [wtp-dev] How to Add TomCat 8 support to Eclipse Keppler



 I also just hit a problem with tomcat 8, and a fix is in the works for
 RC1...

 https://bugs.eclipse.org/bugs/show_bug.cgi?id=425937

 Thanks
--

 *Chuck Bridgham*

  4205 S Miami Blvd

Architect, WebSphere Developer Tools

  Durham, North Carolina 27703-9141

 Eclipse WTP PMC Lead

  USA

 Phone:

 919-254-1848



 Mobile:

 919-345-7657



 e-mail:

 cbrid...@us.ibm.com


--










 From:Humberto Bento hbe...@sinfic.pt
 To:wtp-dev@eclipse.org
 Date:05/09/2014 10:51 AM
 Subject:[wtp-dev] How to Add TomCat 8 support to Eclipse Keppler
 Sent by:wtp-dev-boun...@eclipse.org
  --




 Hi

 I’ve been searching this subject and followed several suggestions, but
 none of them works.
 Example: http://vitalflux.com/add-tomcat-8-eclipse-kepler/

 And I need it

 Anyone can point me in the right directions?

 Thanks


 Atenciosamente,

 *Humberto Bento*
 Gestor de UEN Sistemas de Identidade e Biometria

 O mundo na ponta do dedo, um olhar que faz a diferença.  Biometria,
 soluções que o tornam único.
 The world at the tip of a finger, a look that makes the difference.
 Biometrics, solutions that make you unique.

 *Tlm. (+351) 934 820 014 %28%2B351%29%20934%20820%20014*
 [image: Description: Description: Adobe Systems]

 Rua Kwamme Nhrumah   Av. Dr. Amílcar Cabral, Ed. Pangeia,   Av.
 Olof Palme, nº 358, 1ºEstrada da Ponte, nº2
 nº 10 - 3º, Maianga   Bairro Lalula - Lubango
 Maputo  Quinta Grande -
 Alfragide
 Luanda

  2610-141 Amadora
 * Angola*  *Angola*
  *Moçambique*
 *Portugal*
 Tel: (+244) 222 447 689Tel: (+244) 261 226 110/3
  Tel: (+258) 213 281 82  Tel: (+351) 21 010 39 00
 Fax: (+244) 222 431 139   Fax: (+244) 261 226 115
Fax: (+258) 213 281 82 Fax: (+351) 21 010 39 99

 *www.sinfic.com* http://www.sinfic.com/

 [image: Description: Description: ISO-9001-IQNET]
  ___
 wtp-dev mailing list
 wtp-dev@eclipse.org
 https://dev.eclipse.org/mailman/listinfo/wtp-dev

 ___
 wtp-dev mailing list
 wtp-dev@eclipse.org
 https://dev.eclipse.org/mailman/listinfo/wtp-dev




-- 
Have you tried turning it off and on again - The IT Crowd
___
wtp-dev mailing list
wtp-dev@eclipse.org
https://dev.eclipse.org/mailman/listinfo/wtp-dev

[wtp-dev] Memory leaks in WTP with pending patches

[Fred Bricon]

Hi guys,

Snjeza contributed a few patches to fix some memory leaks in WTP quite some
time ago. These 2 are still pending :

* https://bugs.eclipse.org/399099 Memory leak in EAR5ModelProvider
* https://bugs.eclipse.org/398568 Memory leak in
org.eclipse.jem.workbench.utility.JavaModelListener

Any chance these patches could be applied for Luna M7?

Another memory leak candidate that might be worth looking at (though no
patch was provided) :
* https://bugs.eclipse.org/377998

Thanks,

Fred

-- 
Have you tried turning it off and on again - The IT Crowd
___
wtp-dev mailing list
wtp-dev@eclipse.org
https://dev.eclipse.org/mailman/listinfo/wtp-dev

[wtp-dev] Status of bug fixes for memory leaks in WTP

[Fred Bricon]

Hello World,

about a year ago, Snjezana Peco, from Red Hat, opened a series of bugs
about memory leaks in WTP. She also provided patches to fix them. To this
day, the following bugs are still open :

https://bugs.eclipse.org/bugs/show_bug.cgi?id=398568 target: none
https://bugs.eclipse.org/bugs/show_bug.cgi?id=398599 target: none
https://bugs.eclipse.org/bugs/show_bug.cgi?id=399099 target: none
https://bugs.eclipse.org/bugs/show_bug.cgi?id=399523 target: Dali JPA 3.2.3

Could the WTP team take a look a those and give us a heads up?

Thanks,

Fred Bricon

-- 
Have you tried turning it off and on again - The IT Crowd
___
wtp-dev mailing list
wtp-dev@eclipse.org
https://dev.eclipse.org/mailman/listinfo/wtp-dev

Re: [wtp-dev] Status of bug fixes for memory leaks in WTP

[Fred Bricon]

Thanks for the heads up Neil


On Thu, Feb 6, 2014 at 4:12 PM, Neil Hauge neil.ha...@oracle.com wrote:

  Regarding - https://bugs.eclipse.org/bugs/show_bug.cgi?id=399523 target:
 Dali JPA 3.2.3

 This bug is fixed in all Kepler releases and beyond.  There was never a
 release vehicle to fix this bug in Juno so it is still open against 3.2.3
 if it ever happens.  At this point it could probably be closed since I
 don't think there will be a WTP 3.4.3.

 Neil

  On 2/6/2014 9:47 AM, Fred Bricon wrote:

 Hello World,

  about a year ago, Snjezana Peco, from Red Hat, opened a series of bugs
 about memory leaks in WTP. She also provided patches to fix them. To this
 day, the following bugs are still open :

  https://bugs.eclipse.org/bugs/show_bug.cgi?id=398568 target: none
 https://bugs.eclipse.org/bugs/show_bug.cgi?id=398599 target: none
 https://bugs.eclipse.org/bugs/show_bug.cgi?id=399099 target: none
 https://bugs.eclipse.org/bugs/show_bug.cgi?id=399523 target: Dali JPA
 3.2.3

  Could the WTP team take a look a those and give us a heads up?

  Thanks,

  Fred Bricon

  --
 Have you tried turning it off and on again - The IT Crowd


 ___
 wtp-dev mailing 
 listwtp-dev@eclipse.orghttps://dev.eclipse.org/mailman/listinfo/wtp-dev



 ___
 wtp-dev mailing list
 wtp-dev@eclipse.org
 https://dev.eclipse.org/mailman/listinfo/wtp-dev




-- 
Have you tried turning it off and on again - The IT Crowd
___
wtp-dev mailing list
wtp-dev@eclipse.org
https://dev.eclipse.org/mailman/listinfo/wtp-dev

Re: [wtp-dev] WTP Build issue

[Fred Bricon]

Have you tried latest WTP dev build?
http://download.eclipse.org/webtools/downloads/drops/R3.6.0/I-3.6.0-20140118023607


On Tue, Jan 21, 2014 at 8:29 PM, Norman Cohen nhco...@google.com wrote:

 Fred,

 Any update on this fix? Are you aware of any workarounds (e.g., obtaining
 a jar with the patch or somehow setting the environment so that the call on
 IModelProvider.getModelObject() in
 AbstractMergedModelProvider.getLastModificationTimeOfDDFile() returns a
 non-null EObject with a null eResource)?


 On Tue, Jan 7, 2014 at 3:50 AM, Fred Bricon fbri...@gmail.com wrote:

 Hi,

 Bug 408327 https://bugs.eclipse.org/bugs/show_bug.cgi?id=408327 [1]
 supposedly fixed last may is still showing its ugly face.

 The patch was applied the 28/05/2013 on both master[1] and the 3.5
 branches[2]

 The Kepler SR1, Luna M4 and latest R build (wtp4x-R3.6.0-I:
 I-3.6.0-20140102051318) all contain an
 outdated org.eclipse.jst.jee_1.0.600.v201305131500.jar

 Looking at the git log on that plugin, the only explanation I can come up
 with is the latest commit(s) was not included in any tags. But I'm not
 familiar with WTP's build procedures so there may be another explanation.

 [1] https://bugs.eclipse.org/bugs/show_bug.cgi?id=408327
 [2]
 http://git.eclipse.org/c/jeetools/webtools.javaee.git/commit/?id=865964f2ad5fdf209074cbe8b0db2dce91be19ce
 [3]
 http://git.eclipse.org/c/jeetools/webtools.javaee.git/commit/?h=R3_5_maintenanceid=865964f2ad5fdf209074cbe8b0db2dce91be19ce
 [4]
 http://git.eclipse.org/c/jeetools/webtools.javaee.git/log/plugins/org.eclipse.jst.jee

 Have you tried turning it off and on again - The IT Crowd




 --
 Norman Cohen
 Cloud Platform developer tools
 Google NYC
 nhco...@google.com
 Google Voice: (253) 642-6436 (253-NHCOHEN)




-- 
Have you tried turning it off and on again - The IT Crowd
___
wtp-dev mailing list
wtp-dev@eclipse.org
https://dev.eclipse.org/mailman/listinfo/wtp-dev

[wtp-dev] WTP Build issue

[Fred Bricon]

Hi,

Bug 408327 https://bugs.eclipse.org/bugs/show_bug.cgi?id=408327 [1]
supposedly fixed last may is still showing its ugly face.

The patch was applied the 28/05/2013 on both master[1] and the 3.5
branches[2]

The Kepler SR1, Luna M4 and latest R build (wtp4x-R3.6.0-I:
I-3.6.0-20140102051318) all contain an
outdated org.eclipse.jst.jee_1.0.600.v201305131500.jar

Looking at the git log on that plugin, the only explanation I can come up
with is the latest commit(s) was not included in any tags. But I'm not
familiar with WTP's build procedures so there may be another explanation.

[1] https://bugs.eclipse.org/bugs/show_bug.cgi?id=408327
[2]
http://git.eclipse.org/c/jeetools/webtools.javaee.git/commit/?id=865964f2ad5fdf209074cbe8b0db2dce91be19ce
[3]
http://git.eclipse.org/c/jeetools/webtools.javaee.git/commit/?h=R3_5_maintenanceid=865964f2ad5fdf209074cbe8b0db2dce91be19ce
[4]
http://git.eclipse.org/c/jeetools/webtools.javaee.git/log/plugins/org.eclipse.jst.jee

Have you tried turning it off and on again - The IT Crowd
___
wtp-dev mailing list
wtp-dev@eclipse.org
https://dev.eclipse.org/mailman/listinfo/wtp-dev

Re: [wtp-dev] WTP Build issue

[Fred Bricon]

For the record, the JBoss Tools QA team marked the bugfix as verified on
https://issues.jboss.org/browse/JBIDE-14112.
While I admit we should have notified BZ, that was a false positive so we
would still be in the same situation.
We realized the bug was still active during recent conversations with the
Google Eclipse Plugin team.



On Tue, Jan 7, 2014 at 5:17 PM, Carl Anderson c...@us.ibm.com wrote:

 Folks,

  First, thanks to Roberto for addressing the issue.  Now, irregardless of
 our build system, when a build system is in place, the appropriate build
 process must be followed.  In this case, it wasn't followed.  (In fact, the
 bugzilla process itself wasn't followed, as can be seen by the fact that a
 bug was put up for PMC review without Component lead review, and without
 even being assigned to anyone.)  As can be seen here, not following a
 process can leave WTP in a bad state.  (In this case, something appeared
 fixed that wasn't fixed.)
  Also, I would ask that people verify bugs in a timely manner.  This bug
 was resolved in May of last year, and seven months later we find out it was
 not fixed properly.
  But having said all of that, I also must apologize to Fred - we thought
 this bug had been addressed, and that all was well with the adopter product
 (JBoss Tools), and we do our best to support our adopters.

 FWIW,

 - Carl Anderson
 WTP Build guy

 [image: Inactive hide details for Roberto Sanchez Herrera---01/07/2014
 10:18:09 AM---I just tagged the webtools.javaee repository in Ma]Roberto
 Sanchez Herrera---01/07/2014 10:18:09 AM---I just tagged the
 webtools.javaee repository in Master and R3_5_maintenance, and updated the
 map fil



From:


 Roberto Sanchez Herrera/Mexico/IBM rsanc...@mx1.ibm.com

To:


 General discussion of project-wide or architectural issues. 
 wtp-dev@eclipse.org


Date:


 01/07/2014 10:18 AM

Subject:


 Re: [wtp-dev] WTP Build issue


Sent by:


 wtp-dev-boun...@eclipse.org
 --



 I just tagged the webtools.javaee repository in Master and
 R3_5_maintenance, and updated the map files, using the tags v201401071530
  (Master) and v201401071545 (R3_5_maintenance). The updated plugin should
 be included in the next builds of WTP 3.6 and 3.5.2


 Regards,

 * Roberto Sanchez Herrera*




 From:Fred Bricon fbri...@gmail.com
 To:General discussion of project-wide or architectural issues. 
 wtp-dev@eclipse.org
 Cc:Norman Cohen nhco...@google.com, Rajeev Dayal 
 rda...@google.com, Ludovic Champenois l...@google.com, Alexander Mitin
 alexander.mi...@gmail.com
 Date:07-01-14 02:51
 Subject:[wtp-dev] WTP Build issue
 Sent by:wtp-dev-boun...@eclipse.org
 --



 Hi,

 Bug *408327* https://bugs.eclipse.org/bugs/show_bug.cgi?id=408327 [1]
 supposedly fixed last may is still showing its ugly face.

 The patch was applied the 28/05/2013 on both master[1] and the 3.5
 branches[2]

 The Kepler SR1, Luna M4 and latest R build (wtp4x-R3.6.0-I:
 I-3.6.0-20140102051318) all contain an outdated
 org.eclipse.jst.jee_1.0.600.v201305131500.jar

 Looking at the git log on that plugin, the only explanation I can come up
 with is the latest commit(s) was not included in any tags. But I'm not
 familiar with WTP's build procedures so there may be another explanation.

 [1] 
 *https://bugs.eclipse.org/bugs/show_bug.cgi?id=408327*https://bugs.eclipse.org/bugs/show_bug.cgi?id=408327

 [2]
 *http://git.eclipse.org/c/jeetools/webtools.javaee.git/commit/?id=865964f2ad5fdf209074cbe8b0db2dce91be19ce*http://git.eclipse.org/c/jeetools/webtools.javaee.git/commit/?id=865964f2ad5fdf209074cbe8b0db2dce91be19ce

 [3]
 *http://git.eclipse.org/c/jeetools/webtools.javaee.git/commit/?h=R3_5_maintenanceid=865964f2ad5fdf209074cbe8b0db2dce91be19ce*http://git.eclipse.org/c/jeetools/webtools.javaee.git/commit/?h=R3_5_maintenanceid=865964f2ad5fdf209074cbe8b0db2dce91be19ce

 [4]
 *http://git.eclipse.org/c/jeetools/webtools.javaee.git/log/plugins/org.eclipse.jst.jee*http://git.eclipse.org/c/jeetools/webtools.javaee.git/log/plugins/org.eclipse.jst.jee

 Have you tried turning it off and on again - The IT Crowd
 ___
 wtp-dev mailing list
 wtp-dev@eclipse.org
 *https://dev.eclipse.org/mailman/listinfo/wtp-dev*https://dev.eclipse.org/mailman/listinfo/wtp-dev
 ___
 wtp-dev mailing list
 wtp-dev@eclipse.org
 https://dev.eclipse.org/mailman/listinfo/wtp-dev



 ___
 wtp-dev mailing list
 wtp-dev@eclipse.org
 https://dev.eclipse.org/mailman/listinfo/wtp-dev




-- 
Have you tried turning it off and on again - The IT Crowd
ecblank.gifgraycol.gif___
wtp-dev mailing list
wtp-dev@eclipse.org
https://dev.eclipse.org/mailman/listinfo/wtp-dev

Re: [m2e-wtp-dev] [m2e-users] Overlay Publishing Errors

[Fred Bricon]

What error do you have when referencing the opened project? (workspace
resolution must be turned on on the main web project)


On Wed, Nov 27, 2013 at 1:07 AM, Gaythwaite, James james.gaythwa...@adp.com
 wrote:

 Thanks for the reply. I've tried different combinations of open projects
 with no luck.

 -James

 On Nov 26, 2013, at 6:16 PM, Fred Bricon fbri...@gmail.commailto:
 fbri...@gmail.com wrote:

 This looks like an incompatibility between m2e-wtp's war overlays
 implementation and the Websphere server adapter.
 I can't debug / test Websphere stuff so this is gonna be tricky :-)

 From my limited understanding of the error, there's a chance m2e-wtp 's
 overlay component doesn't behave as expected, being used in a different way
 it has been tested so far (with JBoss / Tomcat / Glassfish). So if anyone
 (hello IBM!)  could help me figure out what's expected from
 https://github.com/eclipse/m2e.wtp/blob/master/org.eclipse.m2e.wtp.overlay/src/org/eclipse/m2e/wtp/overlay/internal/modulecore/OverlayVirtualArchiveComponent.javaplease
  chime in!

 As for the error you see,
 m2e-wtp/overlays/web-resources-6.0.0.5-SNAPSHOT.war tells me you're
 depending on a war archive. As a workaround, you can try having
 web-resources-6.0.0.5-SNAPSHOT opened as a project in your workspace, it
 may work, or not.

 Fred


 On Tue, Nov 26, 2013 at 10:23 PM, Gaythwaite, James 
 james.gaythwa...@adp.commailto:james.gaythwa...@adp.com wrote:
 I am using Eclipse Juno and the latest m2e and wtp plugins for that
 version.  We recently started using war overlays in my project and are
 having a lot of difficulty within the workspace.  If I do a maven update,
 project clean, and start from scratch, the app will start up fine.  After
 that, if I try to publish any changes (doesn't need to be related to the
 overlay projects), I get the following error.  The only way I have gotten
 rid of it is by going back through the update+clean rain dance and then
 doing a server clean.


 Any clue as to what is going wrong?  Thanks!






 The publish encountered some problems and the application may not have
 been installed or it may have been successfully installed but was unable to
 start. View the Details to display the exceptions and server logs that
 occurred during the publish.


 web-ear 


 The application did not update:

 The application did not update:

 For details about the failure, refer to the Console view to see the log
 output of the server. .

 [11/26/13 16:14:23:633 EST] 021f annotations   I
 AroundInvokeMergeAction mergeMethodTarget Could not locate an EJB reference
 for Interceptor  [ com.adp.wfn.system.service.impl.WFNInterceptor ]

 [11/26/13 16:14:26:750 EST] 0223 annotations   I
 AroundInvokeMergeAction mergeMethodTarget Could not locate an EJB reference
 for Interceptor  [ com.adp.wfn.system.service.impl.WFNInterceptor ]

 [11/26/13 16:14:30:112 EST] 0223 annotations   I
 AroundInvokeMergeAction mergeMethodTarget Could not locate an EJB reference
 for Interceptor  [ com.adp.wfn.system.service.impl.WFNInterceptor ]

 [11/26/13 16:14:32:376 EST] 0223 SystemErr R
 org.eclipse.jst.j2ee.commonarchivecore.internal.exception.SaveFailureException:
 m2e-wtp/overlays/web-resources-6.0.0.5-SNAPSHOT.war

 Stack trace of nested exception:

 java.io.FileNotFoundException: File [
 m2e-wtp/overlays/web-resources-6.0.0.5-SNAPSHOT.war ] not found in archive
 [web-process-6.0.0.5-SNAPSHOT.war ] at [
 /home/dev/WAS7.0.0.27/WebSphere70b32/AppServer/profiles/TEST/wstemp/wstemp/app_14296435c35/mrg/web-process-6.0.0.5-SNAPSHOT.war]

 at
 org.eclipse.jst.j2ee.commonarchivecore.internal.strategy.DirectoryLoadStrategyImpl.basicGetInputStream(DirectoryLoadStrategyImpl.java:1009)

 at
 org.eclipse.jst.j2ee.commonarchivecore.internal.strategy.DirectoryLoadStrategyImpl.getInputStream(DirectoryLoadStrategyImpl.java:923)

 at
 org.eclipse.jst.j2ee.commonarchivecore.internal.impl.ContainerImpl.primGetInputStream(ContainerImpl.java:599)

 at
 org.eclipse.jst.j2ee.commonarchivecore.internal.impl.ArchiveImpl.primGetInputStream(ArchiveImpl.java:2022)

 at
 org.eclipse.jst.j2ee.commonarchivecore.internal.impl.FileImpl.getInputStream(FileImpl.java:179)

 at
 org.eclipse.jst.j2ee.commonarchivecore.internal.helpers.FileIteratorImpl.getInputStream(FileIteratorImpl.java:77)

 at
 org.eclipse.jst.j2ee.commonarchivecore.internal.strategy.SaveStrategyImpl.save(SaveStrategyImpl.java:540)

 at
 org.eclipse.jst.j2ee.commonarchivecore.internal.strategy.SaveStrategyImpl.saveFiles(SaveStrategyImpl.java:505)

 at
 org.eclipse.jst.j2ee.commonarchivecore.internal.strategy.SaveStrategyImpl.save(SaveStrategyImpl.java:235)

 at
 org.eclipse.jst.j2ee.commonarchivecore.internal.impl.ArchiveImpl.save(ArchiveImpl.java:2696)

 at
 org.eclipse.jst.j2ee.commonarchivecore.internal.impl.ModuleFileImpl.save(ModuleFileImpl.java:507)

 at
 org.eclipse.jst.j2ee.commonarchivecore.internal.strategy.SaveStrategyImpl.save(SaveStrategyImpl.java:603

Re: [wtp-dev] Tomcat 8 and TomEE support

[Fred Bricon]

 to Tomcat-8 support, it is on my to-do]Larry
 Isaacs ---11/05/2013 04:06:55 PM---Hi Fred, With respect to Tomcat-8
 support, it is on my to-do list including creating a BZ entry.  Th

 From: Larry Isaacs larry.isa...@sas.com
 To: General discussion of project-wide or architectural issues. 
 wtp-dev@eclipse.org,
 Date: 11/05/2013 04:06 PM
 Subject: Re: [wtp-dev] Tomcat 8 and TomEE support
 Sent by: wtp-dev-boun...@eclipse.org
 --





 Hi Fred,

 With respect to Tomcat-8 support, it is on my to-do list including
 creating a BZ entry.  The problem is I’m back to struggling to finding
 enough cycles to get something finished and committed.  I have done some
 initial work that needs a little clean up before it is ready to commit.
  The big unknown is the “Serve Modules without Publishing” feature, as they
 have made major changes to how resources are handled in Tomcat 8.  That
 will likely have to come later.  It’s unclear whether I will get the
 initial work committed for 3.6.0M3.  I have some extra vacation scheduled
 around Thanksgiving, so I should be able to get it into 3.6.0M4 if not in
 M3.

 Cheers,
 Larry

 *From:* wtp-dev-boun...@eclipse.org 
 [mailto:wtp-dev-boun...@eclipse.orgwtp-dev-boun...@eclipse.org]
 *On Behalf Of *Fred Bricon
 * Sent:* Tuesday, November 05, 2013 1:40 PM
 *To:* General discussion of project-wide or architectural issues.
 *Subject:* [wtp-dev] Tomcat 8 and TomEE support

 Hi,

 I vaguely remember reading something, somewhere, about a Tomcat 8 support
 work-in-progress. I couldn't find any related BZ ticket though. What's the
 status on that matter?

 There's one request[1] to add TomEE to the list of supported servers. Do
 you have any plans on adding that to Luna?

 Thanks,

 Fred

 {1] https://bugs.eclipse.org/bugs/show_bug.cgi?id=387733


 --
 Have you tried turning it off and on again - The IT Crowd
 ___
 wtp-dev mailing list
 wtp-dev@eclipse.org
 https://dev.eclipse.org/mailman/listinfo/wtp-dev

 ___
 wtp-dev mailing list
 wtp-dev@eclipse.org
 https://dev.eclipse.org/mailman/listinfo/wtp-dev
 ___
 wtp-dev mailing list
 wtp-dev@eclipse.org
 https://dev.eclipse.org/mailman/listinfo/wtp-dev
 ___
 wtp-dev mailing list
 wtp-dev@eclipse.org
 https://dev.eclipse.org/mailman/listinfo/wtp-dev

 ___
 wtp-dev mailing list
 wtp-dev@eclipse.org
 https://dev.eclipse.org/mailman/listinfo/wtp-dev




-- 
Have you tried turning it off and on again - The IT Crowd
image002.pngimage003.pngimage001.gif___
wtp-dev mailing list
wtp-dev@eclipse.org
https://dev.eclipse.org/mailman/listinfo/wtp-dev

[wtp-dev] Tomcat 8 and TomEE support

[Fred Bricon]

Hi,

I vaguely remember reading something, somewhere, about a Tomcat 8 support
work-in-progress. I couldn't find any related BZ ticket though. What's the
status on that matter?

There's one request[1] to add TomEE to the list of supported servers. Do
you have any plans on adding that to Luna?

Thanks,

Fred

{1] https://bugs.eclipse.org/bugs/show_bug.cgi?id=387733


-- 
Have you tried turning it off and on again - The IT Crowd
___
wtp-dev mailing list
wtp-dev@eclipse.org
https://dev.eclipse.org/mailman/listinfo/wtp-dev

Re: [wtp-dev] How to hint an IServer it should publish stuff?

[Fred Bricon]

Setting the publish state on modules via the internal Server class (haven't
found a public API for that) yields different results depending on the
server adapters.

I'm currently with extremely limited internet/computer access. I'll resume
my experiments and update the status on this issue in about a week or so.
(Only if mosquitoes spare my life in the coming days)
Le 2 août 2013 19:32, Giormov, Dimitar dimitar.gior...@sap.com a écrit :

 Hi,

 Or you can simply do nothing.
 Once the code of the project is changed, the resource change listener will
 detect the change and will mark the module for republish. (there will be a
 label saying [republish] next to the module and the server as far as I can
 remember. So the user can decide whether he/she wants to republish at this
 stage or later. And if the user wants to enable auto republish, it can be
 done in the server editor. Auto republish works only if the server is
 already started I think.

 Best regards,
 Dimitar

 Message: 1
 Date: Fri, 02 Aug 2013 16:57:39 +0800
 From: Rob Stryker rob.stry...@redhat.com
 To: Fred Bricon fbri...@gmail.com
 Cc: General discussion of project-wide or architectural issues.
 wtp-dev@eclipse.org
 Subject: Re: [wtp-dev] How to hint an IServer it should publish stuff?
 Message-ID: 51fb7483.1040...@redhat.com
 Content-Type: text/plain; charset=UTF-8; format=flowed

 As far as I know, there is no API to ensure a publish does not start the
 server.

 You could, however, try to set the module publish state to one of the
 IServer constants indicating an unknown state. This wouldn't force the
 server to publish immediately, but it would tell the server that a
 publish is needed (without forcing the publish to occur).

 I would see this as a bug in the glassfish adapter. IT should support a
 publish without a start, but, I suppose it's entirely up to them how to
 handle their adapter.

 On 07/31/2013 05:46 AM, Fred Bricon wrote:
  Hi,
 
  I have this bug report in m2e-wtp[1], where calling IServer.publish()
  [2] causes some adapter(s) (GlassFish at least) to start stopped
  server instances. I must say I find that behavior questionable, but I
  can't control how 3rd party server adapters work. Anyways, is there a
  recommended way to tell the stopped IServer instance it *should*
  publish, in a way it -most likely- wouldn't start the server?
 
  And if you ask why I force server publication in that resource
  listener, it's to support dynamic war overlay [3] (changes in overlay
  project are automatically published in main web app)
 
  So if you have any pointers, please let me know. Thanks,
 
  Fred.
 
  [1] https://bugs.eclipse.org/bugs/show_bug.cgi?id=413987
  [2]
 
 https://github.com/eclipse/m2e.wtp/blob/master/org.eclipse.m2e.wtp.overlay/src/org/eclipse/m2e/wtp/overlay/internal/servers/OverlayResourceChangeListener.java#L83
  [3] http://maven.apache.org/plugins/maven-war-plugin/overlays.html
 
 
  --
  Have you tried turning it off and on again - The IT Crowd



 --

 ___
 wtp-dev mailing list
 wtp-dev@eclipse.org
 https://dev.eclipse.org/mailman/listinfo/wtp-dev


 End of wtp-dev Digest, Vol 102, Issue 1
 ***
 ___
 wtp-dev mailing list
 wtp-dev@eclipse.org
 https://dev.eclipse.org/mailman/listinfo/wtp-dev

___
wtp-dev mailing list
wtp-dev@eclipse.org
https://dev.eclipse.org/mailman/listinfo/wtp-dev

[wtp-dev] How to hint an IServer it should publish stuff?

[Fred Bricon]

Hi,

I have this bug report in m2e-wtp[1], where calling IServer.publish() [2]
causes some adapter(s) (GlassFish at least) to start stopped server
instances. I must say I find that behavior questionable, but I can't
control how 3rd party server adapters work. Anyways, is there a recommended
way to tell the stopped IServer instance it *should* publish, in a way it
-most likely- wouldn't start the server?

And if you ask why I force server publication in that resource listener,
it's to support dynamic war overlay [3] (changes in overlay project are
automatically published in main web app)

So if you have any pointers, please let me know. Thanks,

Fred.

[1] https://bugs.eclipse.org/bugs/show_bug.cgi?id=413987
[2]
https://github.com/eclipse/m2e.wtp/blob/master/org.eclipse.m2e.wtp.overlay/src/org/eclipse/m2e/wtp/overlay/internal/servers/OverlayResourceChangeListener.java#L83
[3] http://maven.apache.org/plugins/maven-war-plugin/overlays.html


-- 
Have you tried turning it off and on again - The IT Crowd
___
wtp-dev mailing list
wtp-dev@eclipse.org
https://dev.eclipse.org/mailman/listinfo/wtp-dev

Re: [m2e-wtp-dev] Issue with zip files from overlays in the Deployment Assembly

[Fred Bricon]

Alexandre,

Thanks for the patch but please open feature requests over at
https://bugs.eclipse.org/bugs/enter_bug.cgi?product=M2E-WTP and attach
patches using the git format (
http://wiki.eclipse.org/Jetty/Contributor/Contributing_Patches#Git_Format_Patch).
You might also need to signe Eclipse's CLA(
http://wiki.eclipse.org/Development_Resources/Contributing_via_Git) I know
I need to put up some contribution guide somewhere but I'm kinda swamped
right now.

Now the technicalities are out of the way, about the actual solution you
propose :
- first of all, unzip is done only once, unless the source zip changed, in
that case it's unzipped again. so there's no performance overhead here
- performance overhead could occur while scanning the unzipped folder to
determine what's to be published, I grant you that :-)
- now if we serve these unzipped folders directly, we lose
maven-war-plugin's inclusion/exclusion mechanism. It may be a problem for
some.
- I'm aware of some issues with Tomcat's serve without publishing
feature, which doesn't support the overlay components for some reason.
- In any case I don't believe naively serving the unzipped folders is the
*proper* solution. I may revisit my opinion but I need to spend more time
investigating the issue (and please attach a proper patch so I can review
the diffs).
The whole overlay support in m2e-wtp is rather experimental. so things
could be handled completely differently in the future. I'm not excluding
anything just yet.

Unfortunately, I don't think I'll be able to spend some quality time with
your problem before at least mid-august.

Regards,

Fred Bricon


2013/6/27 Alexandre Palma alexandre.pa...@gmail.com

 Hello,
 My name is Alexandre Palma. I work in the RD team of company which
 produces web-based solutions for the financial market.
 We have recently started to adapt our java project's structures to use
 Maven, and we have also adhered to m2e and m2e-wtp, from which we greatly
 benefit, and they have become vital tools in our development process.
 We have, though, a little problem with the way m2e-wtp handles overlays,
 which I've been bypassing by making a little modification to it's source
 code and building in-house versions of it to fit our need, which I believe
 may be the need of other developers as well.

 What happens is that we need our modules to be served without being
 published, and the zip files m2e-wtp attaches to the deployment assembly
 cannot be deployed in this way. But I noticed that m2e-wtp already extracts
 the overlays zip files to the directory target\m2e-wtp\overlays, and if
 those directories be attached to the deployment assembly instead of the zip
 files it works both ways, publishing and not publishing modules.

 The modification I made is in the org.eclipse.m2e.wtp.OverlayConfigurator
 class (which is attached in this message) is to attach those directories to
 the deployment assembly. It was certainly not done in the best possible
 way, given my little understanding of m2e-wtp's architecture and the
 eclipse API itself, but I hope it'll at least help to illustrate what is
 being proposed.

 It'd be greatly appreciated if a change to attach directories instead of
 zip files could be incorporated to m2e-wtp. I believe it would have no
 impact the way it works and it would also  improve performance, since it
 would not have to extract zip files every time the application is published.

 I apologize for my poor English and hope that you could understand what I
 tried to explain.

 Regards and thanks in advance,
 Alexandre


 ___
 m2e-wtp-dev mailing list
 m2e-wtp-dev@eclipse.org
 http://dev.eclipse.org/mailman/listinfo/m2e-wtp-dev




-- 
Have you tried turning it off and on again - The IT Crowd
___
m2e-wtp-dev mailing list
m2e-wtp-dev@eclipse.org
http://dev.eclipse.org/mailman/listinfo/m2e-wtp-dev

Re: [m2e-wtp-dev] Mirroring 1.0.0

[Fred Bricon]

Sorry about that. slf4j and logback were removed from the m2e update site
as per https://bugs.eclipse.org/bugs/show_bug.cgi?id=407797
You must reference the orbit p2 repo in order to grab the proper bits.

Fred


2013/6/19 Ian Trimble ian.trim...@oracle.com

 Unfortunately, there are still a few items missing from my mirrored
 repository:

 **-  **ch.qos.logback.classic

 **-  **ch.qos.logback.core

 **-  **ch.qos.logback.slf4j

 **-  **org.slf4j.api

 ** **

 Without these, m2e-wtp components don’t install. Any advice?

 ** **

 Thanks,

 **-  **Ian

 ** **

 *From:* Ian Trimble
 *Sent:* Tuesday, June 18, 2013 3:22 PM

 *To:* M2E-WTP Developers mailing list
 *Subject:* Re: [m2e-wtp-dev] Mirroring 1.0.0

 ** **

 That looks promising, thanks. I haven’t tried using the mirrored
 repository yet (busy with stuff, you know) but it appears to contain
 everything I expected it to.

 ** **

 Again, thanks,

 **-  **Ian

 ** **

 *From:* Fred Bricon [mailto:fbri...@gmail.com fbri...@gmail.com]
 *Sent:* Tuesday, June 18, 2013 3:03 PM
 *To:* M2E-WTP Developers mailing list
 *Subject:* Re: [m2e-wtp-dev] Mirroring 1.0.0

 ** **

 Can you try  http://download.eclipse.org/m2e-wtp/milestones/kepler/1.0.0/? 
 Version specific p2 sites don't aggregate m2e (I was told to do so for
 the simrel builds)

 ** **

 Categories appear duplicates because the site serves milestones pre/after
 the release review, i.e. with and without the incubation mention, but once
 released you'll only see the incubation-less ones

 ** **

 2013/6/18 Ian Trimble ian.trim...@oracle.com

 Hi,

  

 I used to be able to grab a mirror of the m2e-wtp repository and I would
 get pre-reqs (m2e, etc.) also, but now I seem to only get m2e-wtp, making
 my mirrored repository less-than-useful for my purposes (packaging for
 integration into an adopter product).

  

 Is this an expected change?

  

 If so, what is the recommended method of building a mirrored repository
 (containing m2e-wtp and pre-reqs) now?

  

 Thanks,

 - Ian

  


 ___
 m2e-wtp-dev mailing list
 m2e-wtp-dev@eclipse.org
 http://dev.eclipse.org/mailman/listinfo/m2e-wtp-dev



 

 ** **

 --
 Have you tried turning it off and on again - The IT Crowd 

 ___
 m2e-wtp-dev mailing list
 m2e-wtp-dev@eclipse.org
 http://dev.eclipse.org/mailman/listinfo/m2e-wtp-dev




-- 
Have you tried turning it off and on again - The IT Crowd
___
m2e-wtp-dev mailing list
m2e-wtp-dev@eclipse.org
http://dev.eclipse.org/mailman/listinfo/m2e-wtp-dev

Re: [m2e-wtp-dev] Mirroring 1.0.0

[Fred Bricon]

Can you try  http://download.eclipse.org/m2e-wtp/milestones/kepler/1.0.0/ ?
Version specific p2 sites don't aggregate m2e (I was told to do so for the
simrel builds)

Categories appear duplicates because the site serves milestones pre/after
the release review, i.e. with and without the incubation mention, but once
released you'll only see the incubation-less ones


2013/6/18 Ian Trimble ian.trim...@oracle.com

 Hi,

 ** **

 I used to be able to grab a mirror of the m2e-wtp repository and I would
 get pre-reqs (m2e, etc.) also, but now I seem to only get m2e-wtp, making
 my mirrored repository less-than-useful for my purposes (packaging for
 integration into an adopter product).

 ** **

 Is this an expected change?

 ** **

 If so, what is the recommended method of building a mirrored repository
 (containing m2e-wtp and pre-reqs) now?

 ** **

 Thanks,

 - Ian

 ** **

 ___
 m2e-wtp-dev mailing list
 m2e-wtp-dev@eclipse.org
 http://dev.eclipse.org/mailman/listinfo/m2e-wtp-dev




-- 
Have you tried turning it off and on again - The IT Crowd
___
m2e-wtp-dev mailing list
m2e-wtp-dev@eclipse.org
http://dev.eclipse.org/mailman/listinfo/m2e-wtp-dev

[wtp-dev] Inconsistent feature dependencies in M7

[Fred Bricon]

Hey,

During our building of a target platform for Eclipse M7 we run a validation
of the featuers/dependencies etc.
This normally passes with full glory but this time we caught that a feature
refers to another feature which does not exist (at least not with that
exact
qualifer use)

All the gory details are to be found over at
https://bugs.eclipse.org/bugs/show_bug.cgi?id=407892

Would love to hear if you guys consider this expected behavior - if you do
we'll need to start adding exceptions to our validation;
or if this is a glitch in the build matrix which will be fixed for the next
rev ?

Thanks,


Fred, on behalf of Max Andersen, whose posts never reach this dev list, for
some reason.

-- 
Have you tried turning it off and on again - The IT Crowd
___
wtp-dev mailing list
wtp-dev@eclipse.org
https://dev.eclipse.org/mailman/listinfo/wtp-dev

[m2e-wtp-dev] New m2e-wtp Kepler CI build available

[Fred Bricon]

A new development build of m2e-wtp 1.0.0 for kepler is available from the 
following p2 repository :

http://download.eclipse.org/m2e-wtp/snapshots/kepler/

-- this mail was generated automatically
___
m2e-wtp-dev mailing list
m2e-wtp-dev@eclipse.org
http://dev.eclipse.org/mailman/listinfo/m2e-wtp-dev

[m2e-wtp-dev] New m2e-wtp Juno CI build available

[Fred Bricon]

A new development build of m2e-wtp 0.18.0 for juno is available from the 
following p2 repository :

http://download.eclipse.org/m2e-wtp/snapshots/juno/

-- this mail was generated automatically
___
m2e-wtp-dev mailing list
m2e-wtp-dev@eclipse.org
http://dev.eclipse.org/mailman/listinfo/m2e-wtp-dev

[m2e-wtp-dev] New m2e-wtp Juno CI build available

[Fred Bricon]

A new development build of m2e-wtp 0.18.0 for juno is available from the 
following p2 repository :

http://download.eclipse.org/m2e-wtp/snapshots/juno/

-- this mail was generated automatically
___
m2e-wtp-dev mailing list
m2e-wtp-dev@eclipse.org
http://dev.eclipse.org/mailman/listinfo/m2e-wtp-dev

[m2e-wtp-dev] New m2e-wtp Kepler CI build available

[Fred Bricon]

A new development build of m2e-wtp 0.18.0 for kepler is available from the 
following p2 repository :

http://download.eclipse.org/m2e-wtp/snapshots/kepler/

-- this mail was generated automatically
___
m2e-wtp-dev mailing list
m2e-wtp-dev@eclipse.org
http://dev.eclipse.org/mailman/listinfo/m2e-wtp-dev

Re: [wtp-dev] Requesting jeetools status meeting

[Fred Bricon]

FYI, I created https://bugs.eclipse.org/bugs/show_bug.cgi?id=406447 for the
JAX-RS 2.0 Facet


On Tue, Apr 23, 2013 at 8:18 PM, Fred Bricon fbri...@gmail.com wrote:

 I'll try to chime in, as javaee 7 is a direct concern for m2e-wtp.next

 Fred.
 Le 23 avr. 2013 19:54, Carl Anderson c...@us.ibm.com a écrit :

  Folks,

  I updated http://wiki.eclipse.org/JEE_Status_Meetings - I propose we
 have a meeting at 10 am EDT on April 24th.  The main topic will be the
 current status of our Java EE 7 support, but other topics will be covered
 as needed.

 FWIW,

 - Carl Anderson
 WTP programmer

 [image: Inactive hide details for Rob Stryker ---04/23/2013 06:13:40
 AM---Hi All: Are there still jee-tools status meetings? Looking at]Rob
 Stryker ---04/23/2013 06:13:40 AM---Hi All: Are there still jee-tools
 status meetings? Looking at the website, it



From:


 Rob Stryker rob.stry...@redhat.com

To:


 wtp-dev@eclipse.org

Date:


 04/23/2013 06:13 AM

Subject:


 [wtp-dev] Requesting jeetools status meeting

Sent by:


 wtp-dev-boun...@eclipse.org
 --



 Hi All:

 Are there still jee-tools status meetings? Looking at the website, it
 seems the next one is scheduled for October 10th... ... 2011.  ;)

 I realize everyone is fully swamped lately, but it'd be great if we
 could all synch up a bit this week before lockdown starts coming into
 effect.

 - Rob Stryker

 http://wiki.eclipse.org/JEE_Status_Meetings
 ___
 wtp-dev mailing list
 wtp-dev@eclipse.org
 https://dev.eclipse.org/mailman/listinfo/wtp-dev




 ___
 wtp-dev mailing list
 wtp-dev@eclipse.org
 https://dev.eclipse.org/mailman/listinfo/wtp-dev




-- 
Have you tried turning it off and on again - The IT Crowd
ecblank.gifgraycol.gif___
wtp-dev mailing list
wtp-dev@eclipse.org
https://dev.eclipse.org/mailman/listinfo/wtp-dev

Re: [wtp-dev] Requesting jeetools status meeting

[Fred Bricon]

I'll try to chime in, as javaee 7 is a direct concern for m2e-wtp.next

Fred.
Le 23 avr. 2013 19:54, Carl Anderson c...@us.ibm.com a écrit :

 Folks,

  I updated http://wiki.eclipse.org/JEE_Status_Meetings - I propose we
 have a meeting at 10 am EDT on April 24th.  The main topic will be the
 current status of our Java EE 7 support, but other topics will be covered
 as needed.

 FWIW,

 - Carl Anderson
 WTP programmer

 [image: Inactive hide details for Rob Stryker ---04/23/2013 06:13:40
 AM---Hi All: Are there still jee-tools status meetings? Looking at]Rob
 Stryker ---04/23/2013 06:13:40 AM---Hi All: Are there still jee-tools
 status meetings? Looking at the website, it



From:


 Rob Stryker rob.stry...@redhat.com

To:


 wtp-dev@eclipse.org

Date:


 04/23/2013 06:13 AM

Subject:


 [wtp-dev] Requesting jeetools status meeting

Sent by:


 wtp-dev-boun...@eclipse.org
 --



 Hi All:

 Are there still jee-tools status meetings? Looking at the website, it
 seems the next one is scheduled for October 10th... ... 2011.  ;)

 I realize everyone is fully swamped lately, but it'd be great if we
 could all synch up a bit this week before lockdown starts coming into
 effect.

 - Rob Stryker

 http://wiki.eclipse.org/JEE_Status_Meetings
 ___
 wtp-dev mailing list
 wtp-dev@eclipse.org
 https://dev.eclipse.org/mailman/listinfo/wtp-dev




 ___
 wtp-dev mailing list
 wtp-dev@eclipse.org
 https://dev.eclipse.org/mailman/listinfo/wtp-dev


ecblank.gifgraycol.gif___
wtp-dev mailing list
wtp-dev@eclipse.org
https://dev.eclipse.org/mailman/listinfo/wtp-dev

[wtp-dev] Offline/Local EntityResolver to use?

[Fred Bricon]

Hi,

When I migrated JBoss Tools JSF m2e connector over to m2e-wtp, I removed
the use of JBoss Tools own DTDResolver [1][2], but didn't replace it by
something equivalent from WTP's API.

This bug [3], while not exactly related, reminded me of the situation.
Quickly looking for EntityResolver implementations in WTP's code, I
probably missed some of them but I found at least
* org.eclipse.wst.common.componentcore.internal.impl.WTPEntityResolver
* org.eclipse.jst.j2ee.internal.xml.J2EEXmlDtDEntityResolver
* org.eclipse.jst.j2ee.core.internal.plugin.CatalogJ2EEXmlDtDEntityResolver

All of them are internal classes. Any recommendations on the best way to
proceed here? Should I just fork say, WTPEntityResolver.java into m2e-wtp,
or call wtp's internal class?


[1]
https://github.com/jbosstools/jbosstools-base/blob/master/common/plugins/org.jboss.tools.common.core/src/org/jboss/tools/common/xml/DtdResolver.java#L36
[2]
http://git.eclipse.org/c/m2e-wtp/org.eclipse.m2e.wtp.git/tree/org.eclipse.m2e.wtp.jsf/src/org/eclipse/m2e/wtp/jsf/internal/utils/JSFUtils.java#n127
[3] https://bugs.eclipse.org/bugs/show_bug.cgi?id=405245

Thanks.

Fred Bricon
https://github.com/jbosstools/jbosstools-base/blob/master/common/plugins/org.jboss.tools.common.core/src/org/jboss/tools/common/xml/DtdResolver.java#L36
-- 
Have you tried turning it off and on again - The IT Crowd
___
wtp-dev mailing list
wtp-dev@eclipse.org
https://dev.eclipse.org/mailman/listinfo/wtp-dev

Re: [wtp-dev] Offline/Local EntityResolver to use?

[Fred Bricon]

Do I take that as a blessing to use one of these classes?
If saw, which one do you recommend?



On Tue, Apr 9, 2013 at 3:09 PM, Chuck Bridgham cbrid...@us.ibm.com wrote:

 All of those classes are considered protected  internal api in spite of
 the internal package name.   Changing the namespace would have caused too
 much breakage, so decided to keep as is.

 API policy here:  
 *http://wiki.eclipse.org/WTP_API_Policy*http://wiki.eclipse.org/WTP_API_Policy


 Thanks - Chuck

 Senior Architect, RAD Java EE Tools, WTP PMC Lead
 IBM Software Lab - Research Triangle Park, NC



 From:Fred Bricon fbri...@gmail.com
 To:General discussion of project-wide or architectural issues. 
 wtp-dev@eclipse.org
 Date:04/09/2013 05:30 AM
 Subject:[wtp-dev] Offline/Local EntityResolver to use?
 Sent by:wtp-dev-boun...@eclipse.org
 --



 Hi,

 When I migrated JBoss Tools JSF m2e connector over to m2e-wtp, I removed
 the use of JBoss Tools own DTDResolver [1][2], but didn't replace it by
 something equivalent from WTP's API.

 This bug [3], while not exactly related, reminded me of the situation.
 Quickly looking for EntityResolver implementations in WTP's code, I
 probably missed some of them but I found at least
 * org.eclipse.wst.common.componentcore.internal.impl.WTPEntityResolver
 * org.eclipse.jst.j2ee.internal.xml.J2EEXmlDtDEntityResolver
 * org.eclipse.jst.j2ee.core.internal.plugin.CatalogJ2EEXmlDtDEntityResolver

 All of them are internal classes. Any recommendations on the best way to
 proceed here? Should I just fork say, WTPEntityResolver.java into m2e-wtp,
 or call wtp's internal class?


 [1] *
 https://github.com/jbosstools/jbosstools-base/blob/master/common/plugins/org.jboss.tools.common.core/src/org/jboss/tools/common/xml/DtdResolver.java#L36
 *https://github.com/jbosstools/jbosstools-base/blob/master/common/plugins/org.jboss.tools.common.core/src/org/jboss/tools/common/xml/DtdResolver.java#L36
 [2] *
 http://git.eclipse.org/c/m2e-wtp/org.eclipse.m2e.wtp.git/tree/org.eclipse.m2e.wtp.jsf/src/org/eclipse/m2e/wtp/jsf/internal/utils/JSFUtils.java#n127
 *http://git.eclipse.org/c/m2e-wtp/org.eclipse.m2e.wtp.git/tree/org.eclipse.m2e.wtp.jsf/src/org/eclipse/m2e/wtp/jsf/internal/utils/JSFUtils.java#n127
 [3] 
 *https://bugs.eclipse.org/bugs/show_bug.cgi?id=405245*https://bugs.eclipse.org/bugs/show_bug.cgi?id=405245

 Thanks.

 Fred 
 Briconhttps://github.com/jbosstools/jbosstools-base/blob/master/common/plugins/org.jboss.tools.common.core/src/org/jboss/tools/common/xml/DtdResolver.java#L36
 --
 Have you tried turning it off and on again - The IT Crowd
 ___
 wtp-dev mailing list
 wtp-dev@eclipse.org
 https://dev.eclipse.org/mailman/listinfo/wtp-dev


 ___
 wtp-dev mailing list
 wtp-dev@eclipse.org
 https://dev.eclipse.org/mailman/listinfo/wtp-dev




-- 
Have you tried turning it off and on again - The IT Crowd
___
wtp-dev mailing list
wtp-dev@eclipse.org
https://dev.eclipse.org/mailman/listinfo/wtp-dev

[m2e-wtp-dev] New m2e-wtp Kepler CI build available

[Fred Bricon]

A new development build of m2e-wtp 0.18.0 for kepler is available from the 
following p2 repository :

http://download.eclipse.org/m2e-wtp/snapshots/kepler/

-- this mail was generated automatically
___
m2e-wtp-dev mailing list
m2e-wtp-dev@eclipse.org
http://dev.eclipse.org/mailman/listinfo/m2e-wtp-dev

[m2e-wtp-dev] New m2e-wtp Kepler CI build available

[Fred Bricon]

A new development build of m2e-wtp 0.18.0 for kepler is available from the 
following p2 repository :

http://download.eclipse.org/m2e-wtp/snapshots/kepler/

-- this mail was generated automatically
___
m2e-wtp-dev mailing list
m2e-wtp-dev@eclipse.org
http://dev.eclipse.org/mailman/listinfo/m2e-wtp-dev

[m2e-wtp-dev] New m2e-wtp Kepler CI build available

[Fred Bricon]

A new development build of m2e-wtp 0.18.0 for kepler is available from the 
following p2 repository :

http://download.eclipse.org/m2e-wtp/snapshots/kepler/

-- this mail was generated automatically
___
m2e-wtp-dev mailing list
m2e-wtp-dev@eclipse.org
http://dev.eclipse.org/mailman/listinfo/m2e-wtp-dev

[m2e-wtp-dev] New m2e-wtp Juno CI build available

[Fred Bricon]

A new development build of m2e-wtp 0.18.0 for juno is available from the 
following p2 repository :

http://download.eclipse.org/m2e-wtp/snapshots/juno/

-- this mail was generated automatically
___
m2e-wtp-dev mailing list
m2e-wtp-dev@eclipse.org
http://dev.eclipse.org/mailman/listinfo/m2e-wtp-dev

Re: [m2e-wtp-dev] m2e-wtp 0.17.0 has been released

[Fred Bricon]

... also, see if https://github.com/ifedorenko/p2-browser can help you
troubleshoot the problem
Le 25 févr. 2013 21:54, Fred Bricon fbri...@gmail.com a écrit :

 Hi Ian,

 Sorry for the late reply, I somehow missed your message.

 Unfortunately my p2 fu is pretty much non-existent. It's supposed to work
 though. Nick Boldt managed to mirror the m2e-wtp kepler repo for JBoss,
 maybe he can give you some hints.
 Le 23 févr. 2013 01:54, Ian Trimble ian.trim...@oracle.com a écrit :

 Hello, again.

 ** **

 After further investigation; I **do** see the JPA configurator feature
 in both repositories when I access them via Eclipse, but when I mirror the
 repositories I seem to lose the JPA stuff in Kepler. I’m using the same
 method (”…artifact.repository.mirrorApplication” and
 “…metadata.repository.mirrorApplication”) to mirror both repositories; any
 clue why I fail to get just JPA in my Kepler mirror? Is it perhaps a
 repository configuration issue, or are the p2 applications failing somehow?
 

 ** **

 Any hints are welcomed.

 ** **

 Thanks (again),

 **-  **Ian

 ** **

 *From:* Ian Trimble
 *Sent:* Friday, February 22, 2013 4:37 PM
 *To:* M2E-WTP Developers mailing list
 *Subject:* Re: [m2e-wtp-dev] m2e-wtp 0.17.0 has been released

 ** **

 Hi, Fred.

 ** **

 In the Juno repository, I see the JPA feature/plugin, but I don’t see JPA
 in the Kepler repository. Is this an oversight, or is it packaged
 differently for Kepler?

 ** **

 Thanks,

 **-  **Ian

 ** **

 *From:* Fred Bricon [mailto:fbri...@gmail.com fbri...@gmail.com]
 *Sent:* Wednesday, February 20, 2013 3:41 PM
 *To:* Maven Integration for Eclipse users mailing list; M2E-WTP
 Developers mailing list
 *Cc:* jbosstools-dev
 *Subject:* [m2e-wtp-dev] m2e-wtp 0.17.0 has been released

 ** **

 Hello World!

 ** **

 Hot on the heels of m2e 1.3.1, here comes m2e-wtp 0.17.0.

 0.17.0 is available in 2 flavors : Juno(and Indigo) [1] and Kepler [2]***
 *

 ** **

 The highlight of this release concerns the new JAX-RS, JSF and JPA
 configurators, contributed by JBoss Tools and available as optional
 features. 

 ** **

 See the changelog[3] and New and Noteworthy[4] for more information on
 this release. A somewhat lengthier blog post is published at [5]

 ** **

 As usual please report any bugs to bugzilla[6]

 ** **

 Regards,

 ** **

 Fred 

 ** **

 [1] http://download.eclipse.org/m2e-wtp/releases/juno/ 

 [2] http://download.eclipse.org/m2e-wtp/releases/kepler/

 [3]
 https://bugs.eclipse.org/bugs/buglist.cgi?list_id=4495924query_format=advancedbug_status=RESOLVEDbug_status=VERIFIEDbug_status=CLOSEDproduct=M2E-WTPtarget_milestone=Juno%20SR2%20M1target_milestone=Juno%20SR2%20M2target_milestone=Juno%20SR2%20M3
 

 [4] http://wiki.eclipse.org/M2E-WTP/New_and_Noteworthy/0.17

 [5]
 https://community.jboss.org/en/tools/blog/2013/02/20/m2e-wtp-0170-has-been-released
 

 [6] https://bugs.eclipse.org/bugs/enter_bug.cgi?product=M2E-WTP

 --
 Have you tried turning it off and on again - The IT Crowd 

 ___
 m2e-wtp-dev mailing list
 m2e-wtp-dev@eclipse.org
 http://dev.eclipse.org/mailman/listinfo/m2e-wtp-dev


___
m2e-wtp-dev mailing list
m2e-wtp-dev@eclipse.org
http://dev.eclipse.org/mailman/listinfo/m2e-wtp-dev

[m2e-wtp-dev] m2e-wtp 0.17.0 has been released

[Fred Bricon]

Hello World!

Hot on the heels of m2e 1.3.1, here comes m2e-wtp 0.17.0.
0.17.0 is available in 2 flavors : Juno(and Indigo) [1] and Kepler [2]

The highlight of this release concerns the new JAX-RS, JSF and JPA
configurators, contributed by JBoss Tools and available as optional
features.

See the changelog[3] and New and Noteworthy[4] for more information on this
release. A somewhat lengthier blog post is published at [5]

As usual please report any bugs to bugzilla[6]

Regards,

Fred

[1] http://download.eclipse.org/m2e-wtp/releases/juno/
[2] http://download.eclipse.org/m2e-wtp/releases/kepler/
[3]
https://bugs.eclipse.org/bugs/buglist.cgi?list_id=4495924query_format=advancedbug_status=RESOLVEDbug_status=VERIFIEDbug_status=CLOSEDproduct=M2E-WTPtarget_milestone=Juno%20SR2%20M1target_milestone=Juno%20SR2%20M2target_milestone=Juno%20SR2%20M3
[4] http://wiki.eclipse.org/M2E-WTP/New_and_Noteworthy/0.17
[5]
https://community.jboss.org/en/tools/blog/2013/02/20/m2e-wtp-0170-has-been-released
[6] https://bugs.eclipse.org/bugs/enter_bug.cgi?product=M2E-WTP
-- 
Have you tried turning it off and on again - The IT Crowd
___
m2e-wtp-dev mailing list
m2e-wtp-...@eclipse.org
http://dev.eclipse.org/mailman/listinfo/m2e-wtp-dev

[m2e-wtp-dev] New m2e-wtp Juno CI build available

[Fred Bricon]

A new development build of m2e-wtp 0.17.0 for juno is available from the 
following p2 repository :

http://download.eclipse.org/m2e-wtp/snapshots/juno/

-- this mail was generated automatically
___
m2e-wtp-dev mailing list
m2e-wtp-...@eclipse.org
http://dev.eclipse.org/mailman/listinfo/m2e-wtp-dev

[m2e-wtp-dev] New m2e-wtp Kepler CI build available

[Fred Bricon]

A new development build of m2e-wtp 0.17.0 for kepler is available from the 
following p2 repository :

http://download.eclipse.org/m2e-wtp/snapshots/kepler/

-- this mail was generated automatically
___
m2e-wtp-dev mailing list
m2e-wtp-...@eclipse.org
http://dev.eclipse.org/mailman/listinfo/m2e-wtp-dev

Re: [wtp-dev] Dali version(s) in Kepler M4

[Fred Bricon]

You're right, on a fresh install the correct version is present. I don't
know how my M4 install was tainted with an older version. I'm wondering if
that's caused by installing the stale SDK from
http://download.eclipse.org/webtools/repository/kepler

Getting the SDK matching the kepler release is the reason why I use that
repo BTW.

On Fri, Jan 18, 2013 at 8:36 PM, Neil Hauge neil.ha...@oracle.com wrote:

  Fred,

 I downloaded the latest Java EE Kepler M4 distro to ensure that the right
 code was in there and found the following
 org.eclipse.jpt.jpa.core_3.3.0.v201212061358.jar.That looks right.

 The main Kepler repo (http://download.eclipse.org/releases/kepler/) also
 appears to have the latest content.  This looks good.

 The Webtools Kepler repository (
 http://download.eclipse.org/webtools/repository/kepler) on the other hand
 does appear to have stale Dali content, and likely stale content in
 general.  Given the naming, I would expect that this repo would indeed have
 current WTP milestone bits.  Carl can likely inform us of the current
 nature of this software site and its intended use.

 For now I would use the main Kepler repo to consume Dali and WTP
 milestones.

 Neil




 On 1/18/2013 12:08 PM, Fred Bricon wrote:

 Hi,

  I've been banging my head all day trying to tycho build my m2e-wtp JPA
 plugin against Dali, using the kepler M4 artifacts.
 I've been using the JavaEE Kepler M4 distro to write my code, that distro
 containing org.eclipse.jpt.jpa.core_3.3.0.v201209262323.jar

  When compiling with tycho, I'm using the
 http://download.eclipse.org/releases/kepler and
 http://download.eclipse.org/webtools/repository/kepler repositories to
 fetch m2e-wtp dependencies, and then it starts hitting the fan :

 [INFO] Fetching org.eclipse.jpt.jpa.core_3.3.0.v201212061358.jar.pack.gz from 
 http://mirror.cc.columbia.edu/pub/software/eclipse/releases/kepler/201212210900/plugins/


  That 3.3.0 v201212061358 doesn't
 contain org.eclipse.jpt.jpa.core.platform.JpaPlatformDescription anymore,
 some methods changed/are unavailable, and my plugin doesn't compile.

  So how come http://download.eclipse.org/webtools/repository/keplercontains 
 3.3.0 v201212061358 but the IDE and
 http://download.eclipse.org/webtools/repository/kepler have 
 3.3.0.v201209262323
 ?

  Regards,

  Fred Bricon



  --
 Have you tried turning it off and on again - The IT Crowd


 ___
 wtp-dev mailing 
 listwtp-dev@eclipse.orghttps://dev.eclipse.org/mailman/listinfo/wtp-dev


 ___
 wtp-dev mailing list
 wtp-dev@eclipse.org
 https://dev.eclipse.org/mailman/listinfo/wtp-dev




-- 
Have you tried turning it off and on again - The IT Crowd
___
wtp-dev mailing list
wtp-dev@eclipse.org
https://dev.eclipse.org/mailman/listinfo/wtp-dev

Re: [wtp-dev] Missing webtools p2 update sites break tycho builds

[Fred Bricon]

Thanks Carl, it builds now. The lesson learned here is : composite (stable)
p2  update sites should *never* contain invalid entries.

And sorry about the post to wtp-dev, it struck me I could have used BZ only
after I hit send :-)

Regards,

Fred Bricon



On Thu, Nov 8, 2012 at 5:56 PM, Carl Anderson c...@us.ibm.com wrote:

  Fred,

  First, issues like these are better discussed on wtp-releng, or better
 yet, by opening a bug against WTP Releng.  Having said that, I went through
 and cleaned up all of the references to milestone builds in our repository.
  Can you please retry your build and see if it is working properly now?
  For everyone's information, at some point after the release, we delete
 the milestone builds from download.eclipse.org, in order to reduce WTP's
 footprint there.  Older released builds are also moved to
 archive.eclipse.org.  (And smoke tests are archived and all of that.)  I
 haven't been removing those references from the repository, but that may be
 something that needs to be done now.

 FWIW,

 - Carl Anderson
 WTP Build guy

 [image: Inactive hide details for Fred Bricon ---11/07/2012 09:15:14
 AM---Hi, the m2e-wtp build]Fred Bricon ---11/07/2012 09:15:14 AM---Hi,
 the m2e-wtp build



From:


 Fred Bricon fbri...@gmail.com

To:


 General discussion of project-wide or architectural issues. 
 wtp-dev@eclipse.org

Date:


 11/07/2012 09:15 AM

Subject:


 [wtp-dev] Missing webtools p2 update sites break tycho builds

Sent by:


 wtp-dev-boun...@eclipse.org
 --



 Hi,

 the m2e-wtp *build 
 *http://git.eclipse.org/c/m2e-wtp/org.eclipse.m2e.wtp.git/tree/pom.xml(based
 on tycho 0.16.0) is currently broken because of the following :




 *08:39:53*  [INFO] Adding repository *
 http://download.eclipse.org/webtools/repository/juno*http://download.eclipse.org/webtools/repository/juno

 *08:39:56*  [ERROR] Internal error: java.lang.RuntimeException:
 org.eclipse.equinox.p2.core.ProvisionException: Unable to read repository
 at 
 *http://download.eclipse.org/webtools/repository/juno*http://download.eclipse.org/webtools/repository/juno.
 No repository found at *
 http://download.eclipse.org/webtools/downloads/drops/R3.4.0/S-3.4.0M1-20110812160550/repository
 *http://download.eclipse.org/webtools/downloads/drops/R3.4.0/S-3.4.0M1-20110812160550/repository.
 - [Help 1]
 *08:39:56*  org.apache.maven.InternalErrorException: Internal error:
 java.lang.RuntimeException: org.eclipse.equinox.p2.core.ProvisionException:
 Unable to read repository at *
 http://download.eclipse.org/webtools/repository/juno*http://download.eclipse.org/webtools/repository/juno
 .
 *08:39:56*  at
 org.apache.maven.DefaultMaven.execute(DefaultMaven.java:168)
 *08:39:56*  at org.apache.maven.cli.MavenCli.execute(MavenCli.java:537)
 *08:39:56*  at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:196)
 *08:39:56*  at org.apache.maven.cli.MavenCli.main(MavenCli.java:141)
 *08:39:56*  at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
 *08:39:56*  at
 sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
 *08:39:56*  at
 sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
 *08:39:56*  at java.lang.reflect.Method.invoke(Method.java:597)
 *08:39:56*  at
 org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:290)
 *08:39:56*  at
 org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:230)
 *08:39:56*  at
 org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:409)
 *08:39:56*  at
 org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:352)
 *08:39:56*  Caused by: java.lang.RuntimeException:
 org.eclipse.equinox.p2.core.ProvisionException: Unable to read repository
 at 
 *http://download.eclipse.org/webtools/repository/juno*http://download.eclipse.org/webtools/repository/juno
 .
 *08:39:56*  at
 org.eclipse.tycho.p2.target.TargetPlatformBuilderImpl.addP2Repository(TargetPlatformBuilderImpl.java:247)
 *08:39:56*  at
 org.eclipse.tycho.p2.resolver.P2TargetPlatformResolver.addEntireP2RepositoryToTargetPlatform(P2TargetPlatformResolver.java:314)
 *08:39:56*  at
 org.eclipse.tycho.p2.resolver.P2TargetPlatformResolver.computeTargetPlatform(P2TargetPlatformResolver.java:203)
 *08:39:56*  at
 org.eclipse.tycho.core.resolver.DefaultTychoDependencyResolver.resolveProject(DefaultTychoDependencyResolver.java:94)
 *08:39:56*  at
 org.eclipse.tycho.core.maven.TychoMavenLifecycleParticipant.afterProjectsRead(TychoMavenLifecycleParticipant.java:82)
 *08:39:56*  at
 org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:274)
 *08:39:56*  at
 org.apache.maven.DefaultMaven.execute(DefaultMaven.java:156)
 *08:39:56*  ... 11 more
 *08:39:56*  Caused by: org.eclipse.equinox.p2.core.ProvisionException:
 Unable to read repository at *
 http://download.eclipse.org/webtools/repository/juno*http://download.eclipse.org/webtools/repository/juno
 .
 *08

[wtp-dev] Missing webtools p2 update sites break tycho builds

[Fred Bricon]

.repository.helpers.AbstractRepositoryManager.loadRepository(AbstractRepositoryManager.java:675)*08:39:56*
at 
org.eclipse.equinox.internal.p2.metadata.repository.MetadataRepositoryManager.loadRepository(MetadataRepositoryManager.java:96)*08:39:56*
at 
org.eclipse.equinox.internal.p2.metadata.repository.MetadataRepositoryManager.loadRepository(MetadataRepositoryManager.java:92)*08:39:56*
at 
org.eclipse.tycho.p2.remote.RemoteMetadataRepositoryManager.loadRepository(RemoteMetadataRepositoryManager.java:82)*08:39:56*
at 
org.eclipse.equinox.internal.p2.metadata.repository.CompositeMetadataRepository.addChild(CompositeMetadataRepository.java:167)


The graphical P2 browser from https://github.com/ifedorenko/p2-browser
confirms the canonical webtools repo references several missing repos.
I don't know yet if we can make tycho not fail in cases like this, but
in any case, the aggregate update site at
http://download.eclipse.org/webtools/repository/juno (and possibly
helios/indigo/...) should be cleansed.

Regards,

Fred Bricon


-- 
Have you tried turning it off and on again - The IT Crowd
___
wtp-dev mailing list
wtp-dev@eclipse.org
https://dev.eclipse.org/mailman/listinfo/wtp-dev

Re: [wtp-dev] EGit in Java EE IDE package

[Fred Bricon]

+1

Fred Bricon
Le 11 août 2012 02:45, Konstantin Komissarchik 
konstantin.komissarc...@oracle.com a écrit :

   I noticed that EGit is not included in the Juno Java EE IDE package.
 Given the prominence of Git and the progress of EGit project, should it be
 included?

 Thanks,

 - Konstantin

 ___
 wtp-dev mailing list
 wtp-dev@eclipse.org
 https://dev.eclipse.org/mailman/listinfo/wtp-dev


___
wtp-dev mailing list
wtp-dev@eclipse.org
https://dev.eclipse.org/mailman/listinfo/wtp-dev