Mailing-List: contact notifications-help@ant.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@ant.apache.org
Message-ID: <28291683.68501295477204139.JavaMail.jira@thor>
Date: Wed, 19 Jan 2011 17:46:44 -0500 (EST)
From: "Kevin G (JIRA)" <jira@apache.org>
To: notifications@ant.apache.org
Subject: [jira] Updated: (IVYDE-272) IvyDE deletes entire project!
In-Reply-To: <5471363.68471295477085515.JavaMail.jira@thor>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/IVYDE-272?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Kevin G updated IVYDE-272:
--------------------------

    Description: 
With the "Delete old retrieve artifacts" option active, the IvyDE extension deleted my entire project directory!  The only thing in my workspace project folder is a list of jars (resolved from my ivy file, which was deleted)!!!

After looking into this further, I think this most likely happened because my retrieve pattern did not contain /lib.  It was just:
[artifact]-[revision].[ext]  (I may have had an ivy property on the front as in ${project.lib}/[artifact]-[revision].[ext])

Still, this should never happen!
Luckily, I had everything checked into version control but this could have been a disaster.

-----------------------------------------------------
Steps I took:

I installed IvyDE about 15 minutes ago, via Eclipse Marketplace.  After eclipse restart I right clicked on the project and chose Build Path > Add Libraries > IvyDE Managed Dependencies.

On the main tab, I chose my ivy file from the workspace.
On the settings tab, I enabled project specific settings and chose my settings file and properties file from the workspace.
On the retrieve tab, I enabled project specific settings, chose "do retrieve after resolve" and set my retrieve pattern to the exact value of my ivy.retrieve.pattern variable which was [artifact]-[revsion].[ext] (I may have had a property on the front like ${project.lib} which is in my ivy properties file)
On the advanced tab, I enabled project specific settings and set "order of the classpath entries" to lexical

I clicked FINISHED and it deleted my entire project!!!!!
Leaving only the jars in it's place.

###
 The person fixing this should verify that this does not happen when the retrieve pattern contains an unknown variable such as:
${some.variable}/[artifact]-[revision].[ext]
###

Also, if the artifact variable is going to result in the entire project being deleted, at least a warning should be displayed. Perhaps red text at the bottom that displays:
Warning: all files in the directory /full/path/to/directory/derived/from/retrieve/pattern will be deleted.

Where the full path to the retrieve location is derived based on the retrieve pattern.

Lastly, I would recommend changing the default pattern for types from * to *.jar
That one change, alone, would have prevented this from happening.

  was:
With the "Delete old retrieve artifacts" option active, the IvyDE extension deleted my entire project directory!  The only thing in my workspace project folder is a list of jars (resolved from my ivy file, which was deleted)!!!

After looking into this further, I think this most likely happened because my retrieve pattern did not contain /lib.  It was just:
[artifact]-[revision].[ext]  (I may have had an ivy property on the front as in ${project.lib}/[artifact]-[revision].[ext])

Still, this should never happen!
Luckily, I had everything checked into version control but this could have been a disaster.

-----------------------------------------------------
Steps I took:

I installed IvyDE about 15 minutes ago, via Eclipse Marketplace.  After eclipse restart I right clicked on the project and chose Build Path > Add Libraries > IvyDE Managed Dependencies.

On the main tab, I chose my ivy file from the workspace.
On the settings tab, I enabled project specific settings and chose my settings file and properties file from the workspace.
On the retrieve tab, I enabled project specific settings, chose "do retrieve after resolve" and set my retrieve pattern to the exact value of my ivy.retrieve.pattern variable which was [artifact]-[revsion].[ext] (I may have had a property on the front like ${project.lib} which is in my ivy properties file)
On the advanced tab, I enabled project specific settings and set "order of the classpath entries" to lexical

I clicked FINISHED and it deleted my entire project!!!!!
Leaving only the jars in it's place.

*** The person fixing this should verify that this does not happen when the retrieve pattern contains unknown variable such as:
${unknown.variable}/[artifact]-[revision].[ext]

Also, if the artifact variable is going to result in the entire project being deleted, at least a warning should be displayed. Perhaps red text at the bottom that displays:
Warning: all files in the directory /full/path/to/directory/derived/from/retrieve/pattern will be deleted.

Where the full path to the retrieve location is derived based on the retrieve pattern.

Lastly, I would recommend changing the default pattern for types from * to *.jar
That one change, alone, would have prevented this from happening.


> IvyDE deletes entire project!
> -----------------------------
>
>                 Key: IVYDE-272
>                 URL: https://issues.apache.org/jira/browse/IVYDE-272
>             Project: IvyDE
>          Issue Type: Bug
>          Components: workspace resolver
>    Affects Versions: 2.1.0
>         Environment: Eclipse Version: 3.6.1.r361_v20100909-9gF78GrkFqw7GrsZnvz0JWNTeb6fue6896L Build id: M20100909-0800
> IvyDE Version 2.1.0.201008101807
> Running on MacBook Pro running Mac OS X Leopard 10.6.5
>            Reporter: Kevin G
>            Priority: Critical
>
> With the "Delete old retrieve artifacts" option active, the IvyDE extension deleted my entire project directory!  The only thing in my workspace project folder is a list of jars (resolved from my ivy file, which was deleted)!!!
> After looking into this further, I think this most likely happened because my retrieve pattern did not contain /lib.  It was just:
> [artifact]-[revision].[ext]  (I may have had an ivy property on the front as in ${project.lib}/[artifact]-[revision].[ext])
> Still, this should never happen!
> Luckily, I had everything checked into version control but this could have been a disaster.
> -----------------------------------------------------
> Steps I took:
> I installed IvyDE about 15 minutes ago, via Eclipse Marketplace.  After eclipse restart I right clicked on the project and chose Build Path > Add Libraries > IvyDE Managed Dependencies.
> On the main tab, I chose my ivy file from the workspace.
> On the settings tab, I enabled project specific settings and chose my settings file and properties file from the workspace.
> On the retrieve tab, I enabled project specific settings, chose "do retrieve after resolve" and set my retrieve pattern to the exact value of my ivy.retrieve.pattern variable which was [artifact]-[revsion].[ext] (I may have had a property on the front like ${project.lib} which is in my ivy properties file)
> On the advanced tab, I enabled project specific settings and set "order of the classpath entries" to lexical
> I clicked FINISHED and it deleted my entire project!!!!!
> Leaving only the jars in it's place.
> ###
>  The person fixing this should verify that this does not happen when the retrieve pattern contains an unknown variable such as:
> ${some.variable}/[artifact]-[revision].[ext]
> ###
> Also, if the artifact variable is going to result in the entire project being deleted, at least a warning should be displayed. Perhaps red text at the bottom that displays:
> Warning: all files in the directory /full/path/to/directory/derived/from/retrieve/pattern will be deleted.
> Where the full path to the retrieve location is derived based on the retrieve pattern.
> Lastly, I would recommend changing the default pattern for types from * to *.jar
> That one change, alone, would have prevented this from happening.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.