7:46 p.m.
Hi all,
I am working on developing eclipse windup plugin and trying to bang out
some unit tests for my validator. I would like to take advantage of the
utilities in org.jboss.tools.tests for importing test projects into the
workspace.
Problem is when I add org.jboss.tools.tests to my MANIFEST.MF eclipse
wines that it cannot find that bundle.
What do you all use for a target platform to prevent eclipse from getting
upset and allowing you to leverage content assist and such?
I followed the instructions here,
https://community.jboss.org/wiki/HowToBuildJBossTools40WithMaven3, to
download the Juno target platform, but it does not seem to include the
tests, so that did not help.
Suggestions?
Thanks & Blue Skies,
~Ian
8:50 a.m.
Hi Ian,
For our internal dependencies between jbosstools components, we don't
use the target-platform. Most of JBoss Tools developers have their
dependencies opened as project in the workspace.
for you use-case, you could:
* either import the bundle you depend on in your workspace. The benefit
is that you can see and change its code, which can be helpful, or
* create your own target platform and include into it the test bundles
<location includeAllPlatforms="false" includeMode="slicer"
type="InstallableUnit" includeSource="true">
<repository
location="http://download.jboss.org/jbosstools/updates/nightly/integ...
<unit id="org.jboss.tools.tests" version="0.0.0"/>
<!-- version
0.0.0 will select the best version, so if version changes on site, you
won't need to update it there --> </location>
Hope this helps. Feel free to ask for more if necessary.
You might also discuss with Max (Andersen) about whether your plugin
should already be shaped as a JBoss Tools component and part of a future
JBoss Tools release.
--
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>
2:13 p.m.
On Fri, Oct 04, 2013 at 08:50:54AM +0200, Mickael Istria wrote:
Hope this helps. Feel free to ask for more if necessary.
You might also discuss with Max (Andersen) about whether your plugin
should already be shaped as a JBoss Tools component and part of a
future JBoss Tools release.
yes that is the plan :)
And yes, please target Kepler, not juno as Mickael outlined.
/max
3:48 p.m.
On 10/04/2013 02:13 PM, Max Rydahl Andersen wrote:
yes that is the plan :)
Will this repo become a
jbosstools-windup?
https://github.com/windup/windup-eclipse-plugin
Any ETA of when integration is planned?
--
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>
3:53 p.m.
Well now that the project finally has some junit tests. If you all find
the basic functionality that the project has now useful, I would feel
comfortable having it integrated whenever you all are ready.
As you can see from the issue list on the project I do have a list of
enhancements I would like to do. But I have no idea the next time will be
that I have time to sit down and work on any of them.
Blue Skies,
~Ian
From: jbosstools-dev-bounces(a)lists.jboss.org
[mailto:jbosstools-dev-bounces@lists.jboss.org] On Behalf Of Mickael
Istria
Sent: Friday, October 04, 2013 9:48 AM
To: Max Rydahl Andersen
Cc: jbosstools-dev(a)lists.jboss.org
Subject: Re: [jbosstools-dev] How do I compile against
org.jboss.tools.tests?
On 10/04/2013 02:13 PM, Max Rydahl Andersen wrote:
yes that is the plan :)
Will this repo become a jbosstools-windup?
https://github.com/windup/windup-eclipse-plugin
Any ETA of when integration is planned?
--
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>
11:08 a.m.
On Fri, Oct 04, 2013 at 03:48:07PM +0200, Mickael Istria wrote:
On 10/04/2013 02:13 PM, Max Rydahl Andersen wrote:
>yes that is the plan :)
Will this repo become a jbosstools-windup?
https://github.com/windup/windup-eclipse-plugin
Any ETA of when integration is planned?
When it is ready (and we actually got resources to maintain it etc.)
For now it is just using same dependencies as us so it is possible to use together with
jbds/jbt.
--
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>
3:51 p.m.
Thanks everyone.
I ended up just adding the org.jboss.tools.tests project to my workspace
and that fixed up everything.
Blue Skies,
~Ian
-----Original Message-----
From: jbosstools-dev-bounces(a)lists.jboss.org
[mailto:jbosstools-dev-bounces@lists.jboss.org] On Behalf Of Max Rydahl
Andersen
Sent: Friday, October 04, 2013 8:14 AM
To: Mickael Istria
Cc: jbosstools-dev(a)lists.jboss.org
Subject: Re: [jbosstools-dev] How do I compile against
org.jboss.tools.tests?
On Fri, Oct 04, 2013 at 08:50:54AM +0200, Mickael Istria wrote:
Hope this helps. Feel free to ask for more if necessary.
You might also discuss with Max (Andersen) about whether your plugin
should already be shaped as a JBoss Tools component and part of a
future JBoss Tools release.
yes that is the plan :)
And yes, please target Kepler, not juno as Mickael outlined.
/max
_______________________________________________
jbosstools-dev mailing list
jbosstools-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jbosstools-dev
11:07 a.m.
On Fri, Oct 04, 2013 at 09:51:28AM -0400, Ian Tewksbury wrote:
Thanks everyone.
I ended up just adding the org.jboss.tools.tests project to my workspace
and that fixed up everything.
but does it build via maven ?
Blue Skies,
~Ian
-----Original Message-----
From: jbosstools-dev-bounces(a)lists.jboss.org
[mailto:jbosstools-dev-bounces@lists.jboss.org] On Behalf Of Max Rydahl
Andersen
Sent: Friday, October 04, 2013 8:14 AM
To: Mickael Istria
Cc: jbosstools-dev(a)lists.jboss.org
Subject: Re: [jbosstools-dev] How do I compile against
org.jboss.tools.tests?
On Fri, Oct 04, 2013 at 08:50:54AM +0200, Mickael Istria wrote:
>Hope this helps. Feel free to ask for more if necessary.
>You might also discuss with Max (Andersen) about whether your plugin
>should already be shaped as a JBoss Tools component and part of a
>future JBoss Tools release.
yes that is the plan :)
And yes, please target Kepler, not juno as Mickael outlined.
/max
_______________________________________________
jbosstools-dev mailing list
jbosstools-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jbosstools-dev
5:36 p.m.
Note that
http://download.jboss.org/jbosstools/updates/nightly/integrationtests/4.1...
is a bit out of date - hasn't been updated since May 2013.
A more current build of test dependencies (which does not include the
JBT IS projects) is here:
http://download.jboss.org/jbosstools/updates/nightly/coretests/trunk/
http://download.jboss.org/jbosstools/updates/nightly/coretests/4.1.kepler/
Cheers,
Nick
On 10/04/2013 02:50 AM, Mickael Istria wrote:
Hi Ian,
For our internal dependencies between jbosstools components, we don't
use the target-platform. Most of JBoss Tools developers have their
dependencies opened as project in the workspace.
for you use-case, you could:
* either import the bundle you depend on in your workspace. The benefit
is that you can see and change its code, which can be helpful, or
* create your own target platform and include into it the test bundles
<location includeAllPlatforms="false" includeMode="slicer"
type="InstallableUnit" includeSource="true">
<repository
location="http://download.jboss.org/jbosstools/updates/nightly/integ...
<unit id="org.jboss.tools.tests" version="0.0.0"/>
<!-- version
0.0.0 will select the best version, so if version changes on site, you
won't need to update it there --> </location>
Hope this helps. Feel free to ask for more if necessary.
You might also discuss with Max (Andersen) about whether your plugin
should already be shaped as a JBoss Tools component and part of a future
JBoss Tools release.
--
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>
_______________________________________________
jbosstools-dev mailing list
jbosstools-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jbosstools-dev
--
Nick Boldt :: JBoss by Red Hat
Productization Lead :: JBoss Tools & Dev Studio
http://nick.divbyzero.com
5:37 p.m.
On 10/04/2013 05:36 PM, Nick Boldt wrote:
Note that
http://download.jboss.org/jbosstools/updates/nightly/integrationtests/4.1...
is a bit out of date - hasn't been updated since May 2013.
Thanks Nick for
correcting this wrong link ;)
Since Ian chose to import project in workspace, my bad suggestion
shouldn't have created too much trouble.
--
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>
5:43 p.m.
FWIW, the link you mention is the one that's set by default in the JBT
parent pom, so it's a reasonable one to use.
Really, we ought to get that site building again and keep it up to date,
then release it as part of the upcoming JBT IS 4.1.x release, so it
won't disappear.
On 10/04/2013 11:37 AM, Mickael Istria wrote:
On 10/04/2013 05:36 PM, Nick Boldt wrote:
> Note that
> http://download.jboss.org/jbosstools/updates/nightly/integrationtests/4.1...
> is a bit out of date - hasn't been updated since May 2013.
Thanks Nick for correcting this wrong link ;)
Since Ian chose to import project in workspace, my bad suggestion
shouldn't have created too much trouble.
--
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>
--
Nick Boldt :: JBoss by Red Hat
Productization Lead :: JBoss Tools & Dev Studio
http://nick.divbyzero.com
10:28 a.m.
AFAIR, the main reason the build got broken was some unresolved dependencies of some esb
components - the solution here was to split jbosstools-integration-tests in two. This has
long been sliping away. I promise I will look into that again this week and if there are
no problems there I will coordinate with Andrej and do it.
-Martin
On 4. 10. 2013, at 17:43, Nick Boldt <nboldt(a)redhat.com> wrote:
FWIW, the link you mention is the one that's set by default in
the JBT
parent pom, so it's a reasonable one to use.
Really, we ought to get that site building again and keep it up to date,
then release it as part of the upcoming JBT IS 4.1.x release, so it
won't disappear.
On 10/04/2013 11:37 AM, Mickael Istria wrote:
> On 10/04/2013 05:36 PM, Nick Boldt wrote:
>> Note that
>>
http://download.jboss.org/jbosstools/updates/nightly/integrationtests/4.1...
>> is a bit out of date - hasn't been updated since May 2013.
> Thanks Nick for correcting this wrong link ;)
> Since Ian chose to import project in workspace, my bad suggestion
> shouldn't have created too much trouble.
> --
> 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>
--
Nick Boldt :: JBoss by Red Hat
Productization Lead :: JBoss Tools & Dev Studio
http://nick.divbyzero.com
_______________________________________________
jbosstools-dev mailing list
jbosstools-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jbosstools-dev
--
Martin Malina
JBoss QA Engineer
Red Hat Czech s.r.o.
Purkynova 99
612 45 Brno, Czech Republic
Tel.: +420 532 294 265
11:07 a.m.
On Fri, Oct 04, 2013 at 05:37:43PM +0200, Mickael Istria wrote:
On 10/04/2013 05:36 PM, Nick Boldt wrote:
>Note that
http://download.jboss.org/jbosstools/updates/nightly/integrationtests/4.1...
>is a bit out of date - hasn't been updated since May 2013.
Thanks Nick for correcting this wrong link ;)
Since Ian chose to import project in workspace, my bad suggestion
shouldn't have created too much trouble.
he still need to be able to build with maven so we need something more stable than
"import into workspace" :)
/max
--
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>
_______________________________________________
jbosstools-dev mailing list
jbosstools-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jbosstools-dev
2:23 p.m.
Max,
Once I imported the org.jboss.tools.tests plugin into my workspace the
windup-eclipse-plugin project would compile via mvn clean verify.
I actually found this very interesting. I had expected the import to work
for making Eclipse happy, I had not expected it to make the maven compile
issues happy. I was also surprised that the maven build was not working in
the first place. It never had issues picking up the jbosstools parent, but
for some reason it was having issues picking up the org.jboss.tools.test
plugin. But then as soon as I imported the project into my workspace and
then did a clean verify on the windup-eclipse-plugin its complaining about
not being able to find the test classes went away.
It would be a good experiment to have someone else download the windup
plugin and try a mvn clean verify and see what happens.
Blue Skies,
~Ian
-----Original Message-----
From: jbosstools-dev-bounces(a)lists.jboss.org
[mailto:jbosstools-dev-bounces@lists.jboss.org] On Behalf Of Max Rydahl
Andersen
Sent: Saturday, October 05, 2013 5:07 AM
To: Mickael Istria
Cc: jbosstools-dev(a)lists.jboss.org
Subject: Re: [jbosstools-dev] How do I compile against
org.jboss.tools.tests?
On Fri, Oct 04, 2013 at 05:37:43PM +0200, Mickael Istria wrote:
On 10/04/2013 05:36 PM, Nick Boldt wrote:
>Note that
>http://download.jboss.org/jbosstools/updates/nightly/integrationtests/
>4.1.kepler/ is a bit out of date - hasn't been updated since May 2013.
Thanks Nick for correcting this wrong link ;) Since Ian chose to import
project in workspace, my bad suggestion shouldn't have created too much
trouble.
he still need to be able to build with maven so we need something more
stable than "import into workspace" :)
/max
--
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>
_______________________________________________
jbosstools-dev mailing list
jbosstools-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jbosstools-dev
_______________________________________________
jbosstools-dev mailing list
jbosstools-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jbosstools-dev
10:55 a.m.
On 10/05/2013 02:23 PM, Ian Tewksbury wrote:
Once I imported the org.jboss.tools.tests plugin into my workspace
the
windup-eclipse-plugin project would compile via mvn clean verify.
[...]
I had not expected it to make the maven compile
issues happy. I was also surprised that the maven build was not working in
the first place. It never had issues picking up the jbosstools parent, but
for some reason it was having issues picking up the org.jboss.tools.test
plugin. But then as soon as I imported the project into my workspace and
then did a clean verify on the windup-eclipse-plugin its complaining about
not being able to find the test classes went away.
That's probably not exactly
how it happens ;)
Maven is not aware of you workspace, so the cause of this happiness is
something else. However, it is not possible to figure out the cause
without knowing the error you got ealier.
It would be a good experiment to have someone else download the
windup
plugin and try a mvn clean verify and see what happens.
Better: create a job on
Jenkins CI, so you'll know what happens anytime
you push a commit.
--
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>
10:29 a.m.
On Sat, Oct 05, 2013 at 08:23:14AM -0400, Ian Tewksbury wrote:
Max,
Once I imported the org.jboss.tools.tests plugin into my workspace the
windup-eclipse-plugin project would compile via mvn clean verify.
I actually found this very interesting. I had expected the import to work
for making Eclipse happy, I had not expected it to make the maven compile
issues happy. I was also surprised that the maven build was not working in
the first place. It never had issues picking up the jbosstools parent, but
for some reason it was having issues picking up the org.jboss.tools.test
plugin. But then as soon as I imported the project into my workspace and
then did a clean verify on the windup-eclipse-plugin its complaining about
not being able to find the test classes went away.
That does not make sense. mvn and eclipse dependency resolution is completely
seperate so this should not work ;)
It would be a good experiment to have someone else download the
windup
plugin and try a mvn clean verify and see what happens.
I just git cloned and ran mvn clean verify and I got this:
[INFO] ------------------------------------------------------------------------
[INFO] Reactor Summary:
[INFO]
[INFO] windup.all ........................................ SUCCESS [0.989s]
[INFO] windup.plugins .................................... SUCCESS [0.011s]
[INFO] org.jboss.tools.windup.core ....................... FAILURE [23.230s]
[INFO] windup.features ................................... SKIPPED
[INFO] org.jboss.tools.windup.feature .................... SKIPPED
[INFO] windup.tests ...................................... SKIPPED
[INFO] org.jboss.tools.windup.core.test .................. SKIPPED
[INFO] site .............................................. SKIPPED
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 1:01.472s
[INFO] Finished at: Mon Oct 07 10:27:42 CEST 2013
[INFO] Final Memory: 45M/648M
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal on project org.jboss.tools.windup.core: Could not resolve
dependencies for project
org.jboss.tools.windup.plugins:org.jboss.tools.windup.core:eclipse-plugin:1.0.0-SNAPSHOT:
The following artifacts could not be resolved: org.jboss.windup:windup-engine:jar:0.7.0,
org.jboss.windup:windup-metadata:jar:0.7.0, org.jboss.windup:windup-reporting:jar:0.7.0,
org.jboss.windup:windup-rules:jar:0.7.0: Could not find artifact
org.jboss.windup:windup-engine:jar:0.7.0 in redhat-techpreview-all-repository
(http://maven.repository.redhat.com/techpreview/all/) -> [Help 1]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions, please read the
following articles:
[ERROR] [Help 1]
http://cwiki.apache.org/confluence/display/MAVEN/DependencyResolutionExce...
[ERROR]
[ERROR] After correcting the problems, you can resume the build with the command
[ERROR] mvn <goals> -rf :org.jboss.tools.windup.core
mvn clean verify 30.45s user 2.27s system 50% cpu 1:05.11 total
My guess is you depend on a windup release that is not yet available ?
(or I got some screwed up settings.xml ;)
/max
Blue Skies,
~Ian
-----Original Message-----
From: jbosstools-dev-bounces(a)lists.jboss.org
[mailto:jbosstools-dev-bounces@lists.jboss.org] On Behalf Of Max Rydahl
Andersen
Sent: Saturday, October 05, 2013 5:07 AM
To: Mickael Istria
Cc: jbosstools-dev(a)lists.jboss.org
Subject: Re: [jbosstools-dev] How do I compile against
org.jboss.tools.tests?
On Fri, Oct 04, 2013 at 05:37:43PM +0200, Mickael Istria wrote:
>On 10/04/2013 05:36 PM, Nick Boldt wrote:
>>Note that
>>http://download.jboss.org/jbosstools/updates/nightly/integrationtests/
>>4.1.kepler/ is a bit out of date - hasn't been updated since May 2013.
>Thanks Nick for correcting this wrong link ;) Since Ian chose to import
>project in workspace, my bad suggestion shouldn't have created too much
>trouble.
he still need to be able to build with maven so we need something more
stable than "import into workspace" :)
/max
>--
>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>
>_______________________________________________
>jbosstools-dev mailing list
>jbosstools-dev(a)lists.jboss.org
>https://lists.jboss.org/mailman/listinfo/jbosstools-dev
_______________________________________________
jbosstools-dev mailing list
jbosstools-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jbosstools-dev
1:55 p.m.
Whoops. Yes. Because there is no official release of windup, you first
have to download and build windup. I have updated the instructions to
reflect this.
And yes, I am very aware that it makes zero sense that after importing the
project into eclipse my maven problems went away, hence my shock.
While I don't have the exact text of the error, the gist was a class not
found on a test utility class found in the org.jboss.tools.tests plugin.
And I was getting that same error both from the Eclipse compiler and from
Maven. I expected to get it from Eclipse, but found it strange to be
getting it from maven since maven managed to resolve all of the other
dependencies without issue, and then found it even stranger when after
importing into my workspace maven started working.
I have not yet been introduced to your Jenkins CI for the JBoss tools
projects. If someone wants to point me in its direction and give me the
permissions to set up a job I would be more than happy to. Though I would
bet I could find it off your documentation.
Blue Skies,
~Ian
-----Original Message-----
From: Max Rydahl Andersen [mailto:manderse@redhat.com]
Sent: Monday, October 07, 2013 4:30 AM
To: Ian Tewksbury
Cc: Mickael Istria; jbosstools-dev(a)lists.jboss.org
Subject: Re: [jbosstools-dev] How do I compile against
org.jboss.tools.tests?
On Sat, Oct 05, 2013 at 08:23:14AM -0400, Ian Tewksbury wrote:
Max,
Once I imported the org.jboss.tools.tests plugin into my workspace the
windup-eclipse-plugin project would compile via mvn clean verify.
I actually found this very interesting. I had expected the import to
work for making Eclipse happy, I had not expected it to make the maven
compile issues happy. I was also surprised that the maven build was not
working in the first place. It never had issues picking up the
jbosstools parent, but for some reason it was having issues picking up
the org.jboss.tools.test plugin. But then as soon as I imported the
project into my workspace and then did a clean verify on the
windup-eclipse-plugin its complaining about not being able to find the
test classes
went away.
That does not make sense. mvn and eclipse dependency resolution is
completely seperate so this should not work ;)
It would be a good experiment to have someone else download the windup
plugin and try a mvn clean verify and see what happens.
I just git cloned and ran mvn clean verify and I got this:
[INFO]
------------------------------------------------------------------------
[INFO] Reactor Summary:
[INFO]
[INFO] windup.all ........................................ SUCCESS
[0.989s] [INFO] windup.plugins ....................................
SUCCESS [0.011s] [INFO] org.jboss.tools.windup.core
....................... FAILURE [23.230s] [INFO] windup.features
................................... SKIPPED [INFO]
org.jboss.tools.windup.feature .................... SKIPPED [INFO]
windup.tests ...................................... SKIPPED [INFO]
org.jboss.tools.windup.core.test .................. SKIPPED [INFO] site
.............................................. SKIPPED [INFO]
------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO]
------------------------------------------------------------------------
[INFO] Total time: 1:01.472s
[INFO] Finished at: Mon Oct 07 10:27:42 CEST 2013 [INFO] Final Memory:
45M/648M [INFO]
------------------------------------------------------------------------
[ERROR] Failed to execute goal on project org.jboss.tools.windup.core:
Could not resolve dependencies for project
org.jboss.tools.windup.plugins:org.jboss.tools.windup.core:eclipse-plugin:
1.0.0-SNAPSHOT: The following artifacts could not be resolved:
org.jboss.windup:windup-engine:jar:0.7.0,
org.jboss.windup:windup-metadata:jar:0.7.0,
org.jboss.windup:windup-reporting:jar:0.7.0,
org.jboss.windup:windup-rules:jar:0.7.0: Could not find artifact
org.jboss.windup:windup-engine:jar:0.7.0 in
redhat-techpreview-all-repository
(http://maven.repository.redhat.com/techpreview/all/) -> [Help 1] [ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the
-e switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions,
please read the following articles:
[ERROR] [Help 1]
http://cwiki.apache.org/confluence/display/MAVEN/DependencyResolutionExcep
tion
[ERROR]
[ERROR] After correcting the problems, you can resume the build with the
command
[ERROR] mvn <goals> -rf :org.jboss.tools.windup.core
mvn clean verify 30.45s user 2.27s system 50% cpu 1:05.11 total
My guess is you depend on a windup release that is not yet available ?
(or I got some screwed up settings.xml ;)
/max
Blue Skies,
~Ian
-----Original Message-----
From: jbosstools-dev-bounces(a)lists.jboss.org
[mailto:jbosstools-dev-bounces@lists.jboss.org] On Behalf Of Max Rydahl
Andersen
Sent: Saturday, October 05, 2013 5:07 AM
To: Mickael Istria
Cc: jbosstools-dev(a)lists.jboss.org
Subject: Re: [jbosstools-dev] How do I compile against
org.jboss.tools.tests?
On Fri, Oct 04, 2013 at 05:37:43PM +0200, Mickael Istria wrote:
>On 10/04/2013 05:36 PM, Nick Boldt wrote:
>>Note that
>>http://download.jboss.org/jbosstools/updates/nightly/integrationtests
>>/ 4.1.kepler/ is a bit out of date - hasn't been updated since May
>>2013.
>Thanks Nick for correcting this wrong link ;) Since Ian chose to
>import project in workspace, my bad suggestion shouldn't have created
>too much trouble.
he still need to be able to build with maven so we need something more
stable than "import into workspace" :)
/max
>--
>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>
>_______________________________________________
>jbosstools-dev mailing list
>jbosstools-dev(a)lists.jboss.org
>https://lists.jboss.org/mailman/listinfo/jbosstools-dev
_______________________________________________
jbosstools-dev mailing list
jbosstools-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jbosstools-dev
2:58 p.m.
On Mon, Oct 07, 2013 at 07:55:12AM -0400, Ian Tewksbury wrote:
Whoops. Yes. Because there is no official release of windup, you
first
have to download and build windup. I have updated the instructions to
reflect this.
why don't we get a nightly snapshot build going of windup ?
Then you could use 0.7.0-SNAPSHOT as your dependency and be building out of the box.
Once ready for release you stablize on 0.7.0 or whatever specific version.
/max
And yes, I am very aware that it makes zero sense that after importing the
project into eclipse my maven problems went away, hence my shock.
While I don't have the exact text of the error, the gist was a class not
found on a test utility class found in the org.jboss.tools.tests plugin.
And I was getting that same error both from the Eclipse compiler and from
Maven. I expected to get it from Eclipse, but found it strange to be
getting it from maven since maven managed to resolve all of the other
dependencies without issue, and then found it even stranger when after
importing into my workspace maven started working.
I have not yet been introduced to your Jenkins CI for the JBoss tools
projects. If someone wants to point me in its direction and give me the
permissions to set up a job I would be more than happy to. Though I would
bet I could find it off your documentation.
Blue Skies,
~Ian
-----Original Message-----
From: Max Rydahl Andersen [mailto:manderse@redhat.com]
Sent: Monday, October 07, 2013 4:30 AM
To: Ian Tewksbury
Cc: Mickael Istria; jbosstools-dev(a)lists.jboss.org
Subject: Re: [jbosstools-dev] How do I compile against
org.jboss.tools.tests?
On Sat, Oct 05, 2013 at 08:23:14AM -0400, Ian Tewksbury wrote:
>Max,
>
>Once I imported the org.jboss.tools.tests plugin into my workspace the
>windup-eclipse-plugin project would compile via mvn clean verify.
>
>I actually found this very interesting. I had expected the import to
>work for making Eclipse happy, I had not expected it to make the maven
>compile issues happy. I was also surprised that the maven build was not
>working in the first place. It never had issues picking up the
>jbosstools parent, but for some reason it was having issues picking up
>the org.jboss.tools.test plugin. But then as soon as I imported the
>project into my workspace and then did a clean verify on the
>windup-eclipse-plugin its complaining about not being able to find the
test classes went away.
That does not make sense. mvn and eclipse dependency resolution is
completely seperate so this should not work ;)
>It would be a good experiment to have someone else download the windup
>plugin and try a mvn clean verify and see what happens.
I just git cloned and ran mvn clean verify and I got this:
[INFO]
------------------------------------------------------------------------
[INFO] Reactor Summary:
[INFO]
[INFO] windup.all ........................................ SUCCESS
[0.989s] [INFO] windup.plugins ....................................
SUCCESS [0.011s] [INFO] org.jboss.tools.windup.core
....................... FAILURE [23.230s] [INFO] windup.features
................................... SKIPPED [INFO]
org.jboss.tools.windup.feature .................... SKIPPED [INFO]
windup.tests ...................................... SKIPPED [INFO]
org.jboss.tools.windup.core.test .................. SKIPPED [INFO] site
.............................................. SKIPPED [INFO]
------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO]
------------------------------------------------------------------------
[INFO] Total time: 1:01.472s
[INFO] Finished at: Mon Oct 07 10:27:42 CEST 2013 [INFO] Final Memory:
45M/648M [INFO]
------------------------------------------------------------------------
[ERROR] Failed to execute goal on project org.jboss.tools.windup.core:
Could not resolve dependencies for project
org.jboss.tools.windup.plugins:org.jboss.tools.windup.core:eclipse-plugin:
1.0.0-SNAPSHOT: The following artifacts could not be resolved:
org.jboss.windup:windup-engine:jar:0.7.0,
org.jboss.windup:windup-metadata:jar:0.7.0,
org.jboss.windup:windup-reporting:jar:0.7.0,
org.jboss.windup:windup-rules:jar:0.7.0: Could not find artifact
org.jboss.windup:windup-engine:jar:0.7.0 in
redhat-techpreview-all-repository
(http://maven.repository.redhat.com/techpreview/all/) -> [Help 1] [ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the
-e switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions,
please read the following articles:
[ERROR] [Help 1]
http://cwiki.apache.org/confluence/display/MAVEN/DependencyResolutionExcep
tion
[ERROR]
[ERROR] After correcting the problems, you can resume the build with the
command
[ERROR] mvn <goals> -rf :org.jboss.tools.windup.core
mvn clean verify 30.45s user 2.27s system 50% cpu 1:05.11 total
My guess is you depend on a windup release that is not yet available ?
(or I got some screwed up settings.xml ;)
/max
>Blue Skies,
>
>~Ian
>
>-----Original Message-----
>From: jbosstools-dev-bounces(a)lists.jboss.org
>[mailto:jbosstools-dev-bounces@lists.jboss.org] On Behalf Of Max Rydahl
>Andersen
>Sent: Saturday, October 05, 2013 5:07 AM
>To: Mickael Istria
>Cc: jbosstools-dev(a)lists.jboss.org
>Subject: Re: [jbosstools-dev] How do I compile against
>org.jboss.tools.tests?
>
>On Fri, Oct 04, 2013 at 05:37:43PM +0200, Mickael Istria wrote:
>>On 10/04/2013 05:36 PM, Nick Boldt wrote:
>>>Note that
>>>http://download.jboss.org/jbosstools/updates/nightly/integrationtests
>>>/ 4.1.kepler/ is a bit out of date - hasn't been updated since May
>>>2013.
>>Thanks Nick for correcting this wrong link ;) Since Ian chose to
>>import project in workspace, my bad suggestion shouldn't have created
>>too much trouble.
>
>he still need to be able to build with maven so we need something more
>stable than "import into workspace" :)
>
>/max
>
>>--
>>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>
>
>>_______________________________________________
>>jbosstools-dev mailing list
>>jbosstools-dev(a)lists.jboss.org
>>https://lists.jboss.org/mailman/listinfo/jbosstools-dev
>
>_______________________________________________
>jbosstools-dev mailing list
>jbosstools-dev(a)lists.jboss.org
>https://lists.jboss.org/mailman/listinfo/jbosstools-dev
10:50 a.m.
On 10/05/2013 11:07 AM, Max Rydahl Andersen wrote:
he still need to be able to build with maven so we need something
more
stable than "import into workspace" :)
The windup plugin is using JBT
parent pom, with the right references to
the right sites. So the dependency should resolve fine with Maven, just
like any of the jbosstools-* component.
--
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>
3859
days inactive
3864
days old
jbosstools-dev@lists.jboss.org
18 comments
5 participants
participants (5)
-
Ian Tewksbury -
Martin Malina -
Max Rydahl Andersen -
Mickael Istria -
Nick Boldt