Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Build is broken due to wrong imports #8

Closed
zapbot opened this issue Jun 4, 2015 · 3 comments
Closed

Build is broken due to wrong imports #8

zapbot opened this issue Jun 4, 2015 · 3 comments

Comments

@zapbot
Copy link
Contributor

zapbot commented Jun 4, 2015

What steps will reproduce the problem?
1. Checkout project
2. Change to build directory
3. Execute ant compile

What is the expected output?
Buildfile: build.xml
     [echo] ClassPath=${dist.classpath}

init:
   [delete] Deleting directory /home/duartesilva/workspace/projects/zaproxy/build/build
    [mkdir] Created dir: /home/duartesilva/workspace/projects/zaproxy/build/build

compile:
    [javac] Compiling 324 source files to /home/duartesilva/workspace/projects/zaproxy/build/build
    [javac] Note: Some input files use or override a deprecated API.
    [javac] Note: Recompile with -Xlint:deprecation for details.
    [javac] Note: Some input files use unchecked or unsafe operations.
    [javac] Note: Recompile with -Xlint:unchecked for details.

BUILD SUCCESSFUL
Total time: 10 seconds

What do you see instead?
Buildfile: build.xml
     [echo] ClassPath=${dist.classpath}

init:
   [delete] Deleting directory /home/duartesilva/workspace/projects/zaproxy/build/build
    [mkdir] Created dir: /home/duartesilva/workspace/projects/zaproxy/build/build

compile:
    [javac] Compiling 324 source files to /home/duartesilva/workspace/projects/zaproxy/build/build
    [javac] /home/duartesilva/workspace/projects/zaproxy/src/org/parosproxy/paros/control/Control.java:43:
package org.zaproxy.zap.extension.params does not exist
    [javac] import org.zaproxy.zap.extension.params.ExtensionParams;
    [javac]                                        ^
    [javac] Note: Some input files use or override a deprecated API.
    [javac] Note: Recompile with -Xlint:deprecation for details.
    [javac] Note: Some input files use unchecked or unsafe operations.
    [javac] Note: Recompile with -Xlint:unchecked for details.
    [javac] 1 error

BUILD FAILED
/home/duartesilva/workspace/projects/zaproxy/build/build.xml:29: Compile failed; see
the compiler error output for details.

Total time: 7 seconds

What version of the product are you using? On what operating system?
Revision 172. Linux based.

Please provide any additional information below.
I made the fixes in order for it to build. Bellow is the diff of the changes.

Index: org/parosproxy/paros/control/Control.java
===================================================================
--- org/parosproxy/paros/control/Control.java   (revision 172)
+++ org/parosproxy/paros/control/Control.java   (working copy)
@@ -40,11 +40,11 @@
 import org.zaproxy.zap.extension.compare.ExtensionCompare;
 import org.zaproxy.zap.extension.encoder2.ExtensionEncoder2;
 import org.zaproxy.zap.extension.help.ExtensionHelp;
-import org.zaproxy.zap.extension.params.ExtensionParams;
+//import org.zaproxy.zap.extension.params.ExtensionParams;
 import org.zaproxy.zap.extension.portscan.ExtensionPortScan;
 import org.zaproxy.zap.extension.pscan.ExtensionPassiveScan;
 import org.zaproxy.zap.extension.search.ExtensionSearch;
-import org.zaproxy.zap.extension.test.ExtensionTest;
+//import org.zaproxy.zap.extension.test.ExtensionTest;


 /**

Original issue reported on code.google.com by duartejcsilva on 2010-10-05 17:33:41

@zapbot
Copy link
Contributor Author

zapbot commented Jun 4, 2015

Yes, thats my mistake.
One of the problems with checking in one development while still working on another
one :(
I think I've checked in the right version - does it work ok for you now?

Thanks for reporting this,

Psiinon

Original issue reported on code.google.com by psiinon on 2010-10-05 18:10:09

@zapbot
Copy link
Contributor Author

zapbot commented Jun 4, 2015

(No text was entered with this change)

Original issue reported on code.google.com by psiinon on 2010-10-07 12:09:54

@zapbot zapbot closed this as completed Jun 4, 2015
CashWilliams pushed a commit to CashWilliams/zaproxy that referenced this issue Aug 5, 2015
kingthorin added a commit to kingthorin/zaproxy that referenced this issue Aug 27, 2016
Cleanup so that the CustomPageType enum is actually used, and IDs aren't
dependent upon sequentiality, etc.
kingthorin added a commit to kingthorin/zaproxy that referenced this issue Sep 2, 2016
Cleanup so that the CustomPageType enum is actually used, and IDs aren't
dependent upon sequentiality, etc.
kingthorin added a commit to kingthorin/zaproxy that referenced this issue Sep 18, 2016
Cleanup so that the CustomPageType enum is actually used, and IDs aren't
dependent upon sequentiality, etc.
kingthorin added a commit to kingthorin/zaproxy that referenced this issue Sep 23, 2016
Cleanup so that the CustomPageType enum is actually used, and IDs aren't
dependent upon sequentiality, etc.
kingthorin added a commit to kingthorin/zaproxy that referenced this issue Oct 27, 2016
Cleanup so that the CustomPageType enum is actually used, and IDs aren't
dependent upon sequentiality, etc.
kingthorin added a commit to kingthorin/zaproxy that referenced this issue Oct 27, 2016
Cleanup so that the CustomPageType enum is actually used, and IDs aren't
dependent upon sequentiality, etc.
kingthorin added a commit to kingthorin/zaproxy that referenced this issue Nov 13, 2016
Cleanup so that the CustomPageType enum is actually used, and IDs aren't
dependent upon sequentiality, etc.
kingthorin added a commit to kingthorin/zaproxy that referenced this issue Nov 17, 2016
Cleanup so that the CustomPageType enum is actually used, and IDs aren't
dependent upon sequentiality, etc.
kingthorin added a commit to kingthorin/zaproxy that referenced this issue Jan 20, 2017
Cleanup so that the CustomPageType enum is actually used, and IDs aren't
dependent upon sequentiality, etc.
kingthorin added a commit to kingthorin/zaproxy that referenced this issue Jan 27, 2017
Cleanup so that the CustomPageType enum is actually used, and IDs aren't
dependent upon sequentiality, etc.
kingthorin added a commit to kingthorin/zaproxy that referenced this issue Apr 9, 2017
Cleanup so that the CustomPageType enum is actually used, and IDs aren't
dependent upon sequentiality, etc.
@lock
Copy link

lock bot commented Nov 2, 2019

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.

@lock lock bot locked and limited conversation to collaborators Nov 2, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Development

No branches or pull requests

1 participant