February 2013 - jbosstools-dev - Jboss List Archives

JBoss Tools Core 4.1.0.Alpha1b bits available for QE testing

by Nick Boldt

As always, these are not FINAL bits, but preliminary results for QE testing. Not for redistribution to customers. Update Sites: http://download.jboss.org/jbosstools/updates/JBossTools-4.1.0.Alpha1b.core/ http://download.jboss.org/jbosstools/updates/JBossTools-4.1.0.Alpha1b.web... Builds: http://download.jboss.org/jbosstools/builds/development/4.1.0.Alpha1b.cor... http://download.jboss.org/jbosstools/builds/development/4.1.0.Alpha1b.web... JBoss Central: To test this version of Central, add this to your eclipse.ini file after the -vmargs line: -Djboss.discovery.directory.url=http://download.jboss.org/jbosstools/updates/JBossTools-4.1.0.Alpha1b.core/jbosstools-directory.xml New + Noteworthy: Subject to change, the latest N&N is here: http://htmlpreview.github.com/?https://raw.github.com/jbosstools/jbosstoo... Changes prompting this respin-b are: https://issues.jboss.org/secure/IssueNavigator!executeAdvanced.jspa?jqlQu... -- Nick Boldt :: JBoss by Red Hat Productization Lead :: JBoss Tools & Dev Studio http://nick.divbyzero.com

13 years

1
0
0 / 0

Jasypt xml mapping filies with Jasypt integration.

by Ricardo Rodríguez García

Hello, I have been working in the integration of an extension that would allow the use of Jasypt Hibernate encrypted datatypes with the help of a configuration wizard. I started this project as part of my master thesis and I think is now time to take it to the next level and make it public to address the last issues it migth have and get some feedback from the community. you can have copy of my thesis draft here https://www.dropbox.com/s/12fl73635nad94i/RRGThesis_January%2031%20final%... This would require the addition of Jasypt to the target platform. Please let me know what do you think.

13 years

1
0
0 / 0

New Target Platforms coming for Kepler M5a and Juno SR2 due to EGit 2.3.0 bug

by Nick Boldt

Apologies for yet another TP respin, but needs must due to nasty bug in EGit 2.3.0. http://dev.eclipse.org/mhonarc/lists/jgit-dev/msg02024.html https://issues.jboss.org/browse/JBIDE-13629 Will spin new 4.22.x and 4.30.x target platforms today. -- Nick Boldt :: JBoss by Red Hat Productization Lead :: JBoss Tools & Dev Studio http://nick.divbyzero.com

13 years

1
1
0 / 0

Egit in m5 has a delete all your source by accident bug

by Max Andersen

See http://dev.eclipse.org/mhonarc/lists/jgit-dev/msg02024.html Nick - can we use 2.3.1 instead of 2.3.0 To avoid this nasty bug ? /max (sent from my phone)

13 years

2
1
0 / 0

Introducing Gorkem and aerogear-hybrid component in JBIDE

by Max Rydahl Andersen

Hi all, Some of you already met Gorkem, but for those who haven't he is working on tooling for Aerogear, currently specifically on Hybrid mobile applications using Apache Cordova. I've added a aerogear-hybrid component into https://jira.jboss.org/jira/browse/JBIDE at https://issues.jboss.org/browse/JBIDE/component/12317246 It's utterly empty right now but i'm sure Gorkem and Aerogear will start feeding it issues ;) We'll create a jbosstools-aerogear repository in jbosstools github org once Gorkem is ready for it. Questions ? /max

13 years

3
5
0 / 0

Kind reminder about API Tools

by Mickael Istria

Hi everybody, Soom we'll have API Tools part of the reports produced by build. However, it seems to me that most (all?) JBoss Tools projects don't use API Tools. But it's not too late to start using them in your IDE, in a long-term view, it's very useful and can prevent from some serious bugs and will help you to choose the best version to put for your dependencies in your MANIFEST. Here is a reminder of how to set them up: http://eclipsesource.com/blogs/2013/02/21/api-tools-revisited/ . In our case, the "baseline" is the latest release of JBoss Tools or JBoss Developer Studio. Cheers, -- Mickael Istria Eclipse developer at JBoss, by Red Hat <http://www.jboss.org/tools> My blog <http://mickaelistria.wordpress.com> - My Tweets <http://twitter.com/mickaelistria>

13 years

3
10
0 / 0

New Kepler M5a target platform is available

by Nick Boldt

TP builds are done, parent poms are updated (in master and 4.1.0.Alpha1x branch). We are now on 4.30.4. Now I just need to respin all the jobs to build against the new TP to make sure everything is blue. https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-buildflow... https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-buildflow... On Thu 21 Feb 2013 04:27:37 AM EST, Max Andersen wrote: > Yes. That is the theory :) > > /max (sent from my phone) > > > On 21/02/2013, at 10.11, Martin Malina <mmalina(a)redhat.com > <mailto:mmalina@redhat.com>> wrote: > >> So this will fix JBIDE-13607 >> <https://issues.jboss.org/browse/JBIDE-13607> once propagated to a >> JBDS build? >> >> -Martin >> >> On 21. 2. 2013, at 3:57, Nick Boldt <nboldt(a)redhat.com >> <mailto:nboldt@redhat.com>> wrote: >> >>> Respinning Kepler M5 target platform tonight to pick up newer >>> m2e/m2e-wtp features. When it's done, I'll update the parent pom to >>> point at the new default version, 4.30.4.Alpha1-SNAPSHOT. >>> >>> New sites/zips will be here: >>> >>> http://download.jboss.org/jbosstools/targetplatforms/jbosstoolstarget/ >>> http://www.qa.jboss.com/binaries/RHDS/targetplatforms/jbdevstudiotarget/ >>> >>> Ref: https://issues.jboss.org/browse/JBIDE-13612 -- Nick Boldt :: JBoss by Red Hat Productization Lead :: JBoss Tools & Dev Studio http://nick.divbyzero.com

13 years

1
0
0 / 0

Some modules in jbosstools-4.0.x require version update

by Denis Golovin

I was checking if there are components that requires version update in 4.0.x branch and It looks like some components should have version updated (see attached txt file for component changes): esb ( 1.5.0 - 1.5.1 ) forge ( 1.1.0 - 1.1.1 ) jbpm ( 4.5.0 - 4.5.1 ) openshift ( 2.4.0 - 2.4.1 ) vpe ( 3.4.0 - 3.4.1 ) server/archives ( 3.4.0 - 3.4.1 ) version is already updated in: bpel ( 1.2.0 -> 1.2.1 ) server/as ( 2.4.0 - 2.4.1 ) not sure if it is really required: runtime-soa - nick suggested it can be deleted, because all runtime detection plugins moved to corresponding modules Could component leads confirm if version update above is really required? Thanks Denis

13 years

6
8
0 / 0

m2e-wtp 0.17.0 has been released

by 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=4495924&query_format=ad... [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-bee... [6] https://bugs.eclipse.org/bugs/enter_bug.cgi?product=M2E-WTP -- "Have you tried turning it off and on again" - The IT Crowd

13 years

1
0
0 / 0

m2e 1.3.1 is released

by Fred Bricon

Hi m2e 1.3(.1) is available from the m2e release repository. See [1] for the usual installation instructions. m2e 1.3 focuses on bringing new APIs to be consumed by 3rd party adopters : * New APIs to better control the project conversion to Maven experience - Added new <conversionParticipantConfiguration> extension point to explicitely request ProjectConversionParticipant invocation per packaging type (For Jan and Tobias ;-)) - Added a new ConversionEnabler, providing the ability to preselect the packaging type during project conversion - exclude project conversion participants for certain projects - Added new attributes to order project conversion participants execution * Added new API for Runtime classpath resolution of dependencies referenced with classifiers (fixes some ejb-client resolution issues in m2e-wtp) * Introduced a new ResolverConfiguration#lifecycleMappingId attribute, if specified, the corresponding ILifecycleMapping will be used regardless of any other lifecycle mapping metadata * Introduced a new flavor of AbstractProjectConfigurator#addNature that accepts updateFlags parameter that allows finer control over new nature creation. * Added new AbstractJavaProjectConfigurator#getOutputLocation method to provide better extensibility The following behaviors changed in m2e 1.3 * The behavior for <execute/> mapping of maven plugins has been changed to runOnIncremental=false by default, to prevent random build loops * The JDT conversion participant is now restricted to the “jar” packaging by default. 3rd party adopters need to explicitely request the maven-compiler-plugin to be configured, via an extension point Regular m2e users will probably appreciate : * some slight improvements made on the archetype selection page * import wizard now allows the (de)selection of individual projects See the changelog for everything fixed in the 1.3 version[2]. Since a number of new APIs were introduced in m2e 1.3, we decided to use a separate discovery catalog, to prevent users from installing incompatible m2e extensions in previous 1.1 & 1.2 versions. Unfortunately, some build issues prevented us from getting that catalog ready before the Juno SR2 aggregator build picked m2e 1.3.0 up. For that reason the Juno SR2 distributions and canonical juno p2 repository embed version 1.3.0. m2e 1.3.0 points at the "old" 1.1 discovery catalog. The m2e 1.3.1 version that is available today points at a new 1.3 discovery catalog. The discovery catalog used in m2e can be manually changed by editing your eclipse.ini and adding the -Dm2e.discovery.url parameter -vmargs ... ... -Dm2e.discovery.url=http://download.eclipse.org/technology/m2e/discovery/directory-1.3.xml <http://download.eclipse.org/technology/m2e/discovery/directory-test-1.1.xml> You'll probably notice the new 1.3 catalog contains significantly less entries than the previous version. m2e extensions owner need to make sure their plugins are compatible with m2e 1.3 and request a catalog update in BZ. This time I should be able to take some time to work on the catalog requests backlog. As usual please report any bugs to bugzilla[3] Finally I'd like to give some kudos to Marcos and Roberto from IBM who contributed a number of patches for this release, keep it up guys ;-) Fred [1] http://www.eclipse.org/m2e/download/ [2] https://bugs.eclipse.org/bugs/buglist.cgi?list_id=4327661&query_format=ad... [3] https://bugs.eclipse.org/bugs/enter_bug.cgi?product=M2E -- "Have you tried turning it off and on again" - The IT Crowd

13 years

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-dev February 2013