Open GoogleCodeExporter opened 9 years ago
I've turned the Ant log level to DEBUG and then could see the text below:
--
Adding reference: ant.PropertyHelper
Detected Java version: 1.6 in: /usr/lib/jvm/java-6-sun-1.6.0.16/jre
Detected OS: Linux
...
Setting ro project property: ant.file.{0} (run) ->
/home/luciano/.netbeans/6.7/var/cache/executor-snippets/run.xml
Project base dir set to: /home/luciano/.netbeans/6.7/var/cache/executor-snippets
+Target:
+Target: run
Attempting to create object of type org.apache.tools.ant.helper.DefaultExecutor
Adding reference: ant.executor
Build sequence for target(s) `run' is [run]
Complete build sequence is [run, ]
run:
Setting project property: classpath-translated ->
/home/luciano/NetBeansProjects/IvyTestApplication/build/classes:/home/luciano/Ne
tBeansProjects/IvyTestApplication/src
Override ignored for property "run.jvmargs"
Override ignored for property "work.dir"
Override ignored for property "application.args"
Executing '/usr/lib/jvm/java-6-sun/bin/java' with arguments:
'-Dfile.encoding=UTF-8'
'-classpath'
'/home/luciano/NetBeansProjects/IvyTestApplication/build/classes:/home/luciano/N
etBeansProjects/IvyTestApplication/src'
'ivytestapplication.Main'
The ' characters around the executable and arguments are
not part of the command.
...
---
As can be seen, the the jar files downloaded by Ivy are not part of classpath,
and
only the run task is executed. The -ivy-retrieve task or any ivybeans related
task is
not part of build sequence.
Is there any workaround while the fix is not released?
Original comment by lcbarcel...@gmail.com
on 14 Sep 2009 at 3:34
Well, I finally found a simple workaround. Just turn off the "Compile On Save"
at
project preferences for Run and Debug start working.
It seems Netbeans use that .../executor-snippets/run.xml to define the run task
and
.../executor-snippets/debug.xml to define the debug task when "Compile on Save"
is
active.
What's the fix? Is Ivybeans missing to fulfill some requirement for working with
"Compile on save" or is Netbeans missing something when implementing that
feature?
Original comment by lcbarcel...@gmail.com
on 14 Sep 2009 at 1:47
Thanks for the workaround. The question is good. How works the maven plugin in
this
case?
Original comment by oliver.n...@gmail.com
on 14 Sep 2009 at 3:30
I have the same kind of trouble with the maven support. When I want to be sure
that my
test will be launched correctly I often put the compile on save off.
I will investigate and try to find the guilty ;).
Thanks for that.
Original comment by laurent....@gmail.com
on 14 Sep 2009 at 4:08
Original comment by laurent....@gmail.com
on 14 Sep 2009 at 4:08
Issue 78 has been merged into this issue.
Original comment by bruce.ch...@gmail.com
on 9 Sep 2010 at 4:57
so does Compile-on-save feature not work with ClassPathProvider mechanism in
general, or does our ClassPathProviderImpl specifically not work properly with
it.
I am assuming that it is only the run action for which there are problems
between COS and ivybeans.
Will do some experiments to answer above questions.
Original comment by bruce.ch...@gmail.com
on 9 Sep 2010 at 10:13
Original issue reported on code.google.com by
oliver.n...@gmail.com
on 11 Sep 2009 at 8:39